3 ms·

1. You don't 'lose' the pods. If your pod fails on liveness or readiness checks it restarts, over and over until it passes. 2. Depends on your team for sure. I

1. You don't 'lose' the pods. If your pod fails on liveness or readiness checks it restarts, over and over until it passes. 2. Depends on your team for sure. If you are on a team that's like "We'll just spin this up and it will be fine." you ignore the fact that 'things happen'. I've seen similar situations with companies that deploy on bare linux servers as well, some update breaks something or something isn't optimally configured. Things go wrong with systems, people who know the systems are needed to fix them. It sounds like if you intend on using kubernetes you should learn to troubleshoot it. It's not difficult to find people who know how to actually run kubernetes, it's just hard to convince them to switch jobs for you. I get a decent numbers of cold, non recruiter, linkedin contacts a month, and frankly many recruiters... but my current job pays well and matches my worklife balance. Zero people who are reaching out from startups offer the whole package, they can usually come in fine on the money, but I'm not working a hundred hours a week with little to no support. On the 'established corporate enterprise' side of the house, they can be inflexible when it comes to vacation time, salary ranges etc. but I've found a good place.

kule 4y ago
RE 1. Just to be precise (as I thought this until recently): * liveness check will cause pod restarts. * Readiness check causes the pod to be removed from the round-robin of new traffic requests so it has time to recover/finish processing what it's working on.
- sleepybrett 4y ago
  You are correct, readiness removes it from any service objects it would be an endpoint to. My point was more 'the pod doesn't go away'. I've seen some people do stuff with the HPA that could cause it to scale down to minimum replicas if its in a broken state, depending on what stats you are using to scale, but that's more of a 'kubernetes doing what you told it to do' problem.

kule 4y ago

RE 1. Just to be precise (as I thought this until recently): * liveness check will cause pod restarts. * Readiness check causes the pod to be removed from the round-robin of new traffic requests so it has time to recover/finish processing what it's working on.

sleepybrett 4y ago
You are correct, readiness removes it from any service objects it would be an endpoint to. My point was more 'the pod doesn't go away'. I've seen some people do stuff with the HPA that could cause it to scale down to minimum replicas if its in a broken state, depending on what stats you are using to scale, but that's more of a 'kubernetes doing what you told it to do' problem.