Working with Kubernetes is fun when your Kubernetes cluster is up and your nodes are working as you expected. But as a DevOps enthusiast who follows the principles of Continuous Integration and Continuous Delivery, you are aware that new changes or feature requests are always coming through the Jenkins Pipeline, and …

TL;DR One pod: kubectl delete pod NAME -n NAMESPACE. If a Deployment owns it, the ReplicaSet creates a replacement within seconds; in my run the delete took 2.3 seconds and the new pod was Running 5 seconds later. All pods in a namespace: kubectl delete pods --all -n NAMESPACE. Owned pods come back, bare pods are gone …

TL;DR A deleted pod comes back because a controller owns it. On my test cluster the ReplicaSet replaced the pod 9 seconds after kubectl delete pod. Deleting the ReplicaSet does not help either - the Deployment recreated it within 5 seconds. Find the owner in one command: kubectl get pod <name> -o …

Helmfile is an another wrapper working on top of Helm Chart. Just like Helm Chart, Helmfile also uses the YAML for writing the configurations. But why do you need Helmfile if you are working with Kubernetes and Helm Chart? Here are some key benfits of using Helmfile - You can bundle several Helm Charts into a Single …

I have been using vagrant for quite some time on my development laptop for work as well as for learning purposes. But one thing which I noticed working with Vagrant is you have to use vagrant ssh every time whenever you want to login into your virtual machine and in case if you have multiple virtual machine configured …

Vagrant helped developers to create a very lightweight, portable development machine which can be destroyed and recreated on the fly. When it comes to starting a virtual machine onto your development environment vagrant helps you to spin up the virtual machine with very few lines of codes. But while working with …

Maintaining a healthy kubernetes cluster is really challenging especially if you have not configured the Liveness, Readiness and Startup Probes correctly for your containers deployed under kubernetes containers. If I have to put in a simple way - Liveness probes - It is responsible for restarting your container, if it …

As DevOps, we often make quite a lot of mistakes and one of the most oversight mistakes we generally do is forget to expose a port for the container. When you realize that you have not exposed any port for the container then you start looking for ways to change the port mapping of a live container or in other words, …

When we package any application using Docker then either we create Dockerfile or docker-compose.yaml, even you can create both the files and share the files with others. There is one important aspect in both the files .i.e. PORT. Any container which you build and ship to other developers has to have one or more …

I usually work with multiple projects at once and whenever there is a new feature on which I had to work, I usually create a new Branch from my Master branch and once I am done with the new feature I do create a pull request and after the approval, I do merge my changes from my new Branch to my Master branch. Well, …