3 min read
In the same way we can use git blame to identify who and when has modified a specific line, with kubectl blame we'll be able to do the same to Kubernetes objects
13/05/2022
Read more...2 min read
On a Kubernetes cluster we might have deprecated versions of the object, so after updating it we might end up with something not properly working:
$ kubectl api-resources | grep Ingress\$
ingresses ing extensions/v1beta1 true Ingress
ingresses ing networking.k8s.io/v1 true Ingress
23/09/2021
Read more...2 min read
If we need to take a look at the resources of a Kubernetes cluster, by using kubectl get all we won't be able to see all the resources. Most notably, it won't list Ingress objects. You can take a look at this issue for kubectl for the details but we won't be able to get all the resources using this command, we'll have to install the get-all krew plugin
14/09/2021
Read more...2 min read
Some kubernetes objects creates and manages other kubernetes objects in order to provide it's functionality. For example, the Deployment object creates a ReplicaSet that in turn creates the desired Pod objects. We can always track down this relationship using kubectl describe but using the tree krew plugin we can see the relationship in a visual way. We can install it like so:
$ kubectl krew install tree
14/06/2021
Read more...2 min read
Krew is a plugin manager for kubectl (v1.12 or higher), we will need to install krew first. To be able to test the unused-volumes plugin we will have to create a PersistentVolumeClaim that we won't use on any pot:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: demo-pvc
namespace: kube-system
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
13/01/2021
Read more...