restartPolicy: never - How to kill an entire K8s cluster with an innocent mistake! (1/2)

Killing an entire Kubernetes Cluster just from an innocent misconfiguration could be the most expensive Kubernetes-related mistake you'll ever make. Now, I apologize for the click-baity title, but what I'm about to show you is something I've observed at a real-life client: An innocent misconfiguration on a Kubernetes Job Template managed to destroy an entire production cluster leading to downtime of production apps.

[@panteliskaramolegkos2693]

I think this can be addressed with backOffLimit setting (?)

[@ansontong560]

Waiting for your next video =]

[@davronsherbaev9133]

Waiting for second part)

[@cynikalX]

video ends with "... in the next video" but this was 3 months ago and no new videos? :-( hope you're ok?

[@kubucation]

Sorry, have been wanting to upload part 2, but have just been too busy with „real“ work ;)

[@gennwayo7934]

part two still not uploaded :(

[@kubucation]

You’re right I must have forgotten about that. I did record it, but I think never edited it. Let me see if I still have the recording.