3 min read
If we have a set of resources on a set of terraform code that we want to move to another code base, we could use terraform import to import them to the new state but this required make the effort to identify the resources to import. If are going to import the entire state we can make it much easier using terraform state pull and terraform state push
30/09/2021
Read more...3 min read
If you are using a mixed policy on your EKS workers ASG you will want to install the AWS node termination handler to drain a node once AWS notifies that a particular spot instance is going to be reclaimed
29/09/2021
Read more...3 min read
Using buildx we can build multi architecture containers, we can use a github action to automatically build it
28/09/2021
Read more...3 min read
Using a webhook we can mutate Kubernetes objects when they are inserted to the cluster. But using a mutating operator can save us the trouble of having to actually code how the object needs to be patched
27/09/2021
Read more...2 min read
If we need to execute some actions at container startup of before stopping the container we can me use of the container lifecycle hooks
24/09/2021
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...3 min read
If we try to provision a gp3 Volume using a PVC on an EKS cluster we might get the invalid AWS VolumeType "gp3" error. This means we are using an outdated EBS CSI
21/09/2021
Read more...2 min read
The default StorageClass is defined using the storageclass.kubernetes.io/is-default-class annotation as follows:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
storageclass.kubernetes.io/is-default-class: "true"
(...)
To be able to change it we will have to removed from the current default and set it to the new one.
20/09/2021
Read more...2 min read
For a long time we were not able to properly monitor the progress of a dd command unless we were using pv of having another process to periodically send a SIGUSR1 to the dd process
17/09/2021
Read more...3 min read
If saving up to 90% for the same instance type is no reason enough to start using spot instances, to be able to use the same AutoScalingGroup to spawn both types of instances, saving us from the hassle of having to manage it by ourselves might help to change your mind
16/09/2021
Read more...