I was reading a post, where someone posted this question. I wanted to check with Tailwinds customers if they really perform CI/CD. Some really interesting answers that I would like to share here. But before getting onto the details, few definitions and disclaimers. I don’t really want to get into…

This RANT is based on tailwinds.ai interactions with SREs/DevOps teams across different organizations. Few common trends we notice are DevOps/SREs are either part of one team or folded towards a single hierarchy. So would have used DevOps & SREs interchangeably in this blog. DevOps/SREs typically tend to be passive and…

Recently, Daniel Polencic posted a lovely article on Autoscalers, this triggered some thoughts, hence writing this quick short note as a response to Daniel’s article. Need For Autoscalers. We observe that autoscalers are typically needed for a couple of use cases, they are In a highly dynamic environment where there is a large…

Recently, I was debugging two completely different Pod crash scenarios. In the first case, the Pod got into CrashLoopBackOff almost immediately after it got created while in another case the pod was killed randomly after running for a few days. I spent about an hour to determine the root cause…

Most Kubernetes users would have encountered OOMKilled at least once. When OOMKilled occurs, we tend to recalibrate the pod’s QoS or move the pod to a different node thinking there is a memory issue with the node. …

Kubernetes is a platform that one needs to morph to make it work. As part of personalizing effort, having a strategy to handle node failure cases becomes an important criterion. To implement such a blueprint, one needs to understand how different controllers behave when a node fails. …

We understand What happens to pods when nodes fail? but would also want the Kubernetes system to react faster when nodes fail to make the system robust in terms of availability and reliability. Let’s understand the flow of events and learn about related timers before tweaking them. Events Observed When Node Becomes Unhealthy. Derived Retry Parameter. node-status-update-frequency is a…

There are many use-cases where Pod delete requires to be handled gracefully. Few examples are; logs of the deleting pod to be stored in a remote location, Current requests/jobs to be processed before Pod deletes, or update certain rules/fields before shut down. Such use-cases require an understanding of how the…