Following the path of our idol @PawanKalyan Garu
We decided to donate 1,00,000 rupees to the young kid Niranjan personally from our side.
And we also pledge to donate 5% of the Profit from the Panjaa Re Release to support our beloved kid Niranjan for his medical care.
#Peddi New Scenes Update
From today’s second shows onwards, the new scenes are playing in updated theatres.
From tomorrow, all locations will screen the enhanced version ❤️
More emotion. More depth. More PEDDI.
#RamCharan
East Godavari Day 2 - ALL TIME RECORD 🔥
#PEDDI Collected 1.16cr Share in East Godavari on Day 2, The Highest Among All Thursday Release Movies 🔥🔥👌
Mr.BoxOffice on Duty @AlwaysRamCharan 🔥
Champions ⭐️⭐️⭐️ Phenomenal win for Team India in Ahmedabad. Absolutely no match for the explosive cricket played by us throughout the tournament. Brilliant character shown by the boys to keep fighting in tough situations and become world champions once again. Congratulations to all the players and all the members of the management for achieving this feat. Jai Hind 🇮🇳❤️
Tell me about a time something broke in production. What did you do? How did you prevent it from happening again?
Every DevOps interview has this question.
Most candidates fumble it. Not because they lack experience. Because they never learned how to tell the story properly.
Here is a real one from my production environment that I taught in my Devops Bootcamp today 👇
One morning, I got an early alert. Users were complaining that the application was slow or completely inaccessible.
I opened my IDE, pulled up the cluster. Checked pods. All green. Checked services. Fine. Checked ingress. No issues. Everything looked perfectly healthy.
But users still could not access the app.
Before I get into the troubleshooting, here is the context.
We run a stateful workflow automation platform on EKS. It has six components that must start in a strict order. If the first one does not come up, nothing after it starts either.
Here is how I troubleshoted it.
Since the pods looked healthy at the surface level, I went deeper. We had a script that would log inside each component pod and pull an internal health report. I ran it.
The report showed that the first component in the chain was not actually connecting to anything. It was running but not working.
I described the pod and checked the events. The volume was not mounting to the node.
I checked the node. The CSI driver pod was unhealthy. The CSI driver is what allows a Kubernetes node to attach EBS volumes. Without it the node cannot mount any storage.
No storage mount means the first component cannot start. First component does not start means nothing else in the chain starts either.
I identified the bad node and terminated it so a fresh one could come up.
But then I hit a second problem.
The volume was still locked to the old node. The new node was trying to attach the same volume and getting blocked.
This is called a multi-attach error. EBS volumes can only be attached to one node at a time.
I had to find the stuck volume attachment and delete it manually.
Once that was cleared, the new node claimed the volume cleanly.
The first component started. Everything else followed in order.
.
.
Want the complete RCA for this incident, including the root cause, the five whys breakdown, and the exact prevention steps.
Then do these 3 things 👇
1. Follow me,
2. Retweet this
3. Comment RCA
I will send it to your DM
Terraform is the one skill that separates DevOps engineers who click through consoles from those who deploy infrastructure in seconds.
I've had written a comprehensive "Terraform Handbook for DevOps Engineers" ebook that thousands of people loved
and I'm giving it away for free.
To get it for free, just do 3 things.
✓ Follow me (for DM access)
✓ Retweet this post
✓ Comment "Terraform"
And I will personally send you that.
P.S. If i missed sending you due to some issues, just DM me and I will share