3 min read
If we have some of the infrastructure that were created manually we can still import it into the terraform state. This ensures you can have a smooth transition from manually created resources to Infrastructure as Code
To do so we will be using then terraform import command:
$ terraform import
The import command expects two arguments.
Usage: terraform import [options] ADDR ID
(...)
04/05/2021
Read more...2 min read
While performing any action we might encounter the following error:
error: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
03/05/2021
Read more...3 min read
Terraform keeps a list of managed objects on it's state, if for some reason we no longer want terraform to manage them we can remove them from the code base. Doing so we will see how terraform will try to delete them:
$ terraform plan
(...)
Plan: 0 to add, 0 to change, 10 to destroy.
(...)
30/04/2021
Read more...1 min read
Using kubectl drain you can evict pods and disabled scheduling for a node so you can proceed with some maintenance. Once this maintenance is over we will need to allow pods to be scheduled to this node, removing the SchedulingDisabled:
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
nauvoo.pet2cattle.com Ready control-plane,master 19d v1.20.4+k3s1
tycho.pet2cattle.com Ready,SchedulingDisabled <none> 9m25s v1.20.4+k3s1
29/04/2021
Read more...2 min read
Using the AWS CLI we can perform most operations for files sitting on a S3 bucket such as: list, copy, rename, cat, etc...
28/04/2021
Read more...