Bart Farrell: Who are you? What's your role? And where do you work?
Max Majander: Hello, Bart. My name is Max. I'm head of sales and partnerships at Kumorion.
Bart Farrell: In terms of the work that you're doing, what are the number one problems that the people that you're working with are facing when it comes to working with Kubernetes?
Max Majander: There can be many issues when you're trying to run your own Kubernetes. What we're trying to do for companies is to give them a managed platform that's easy to use, easy to scale, and that's where we really excel. We have 15 years of experience running Kubernetes.
Bart Farrell: A Kubernetes setting can look wrong but still feel risky to change once it's already in production. Requests, limits, autoscaling or probes? What would you tell a team that sees the problem but is nervous that the fix could cause an outage?
Max Majander: I would start by taking a breath because you don't want to be guessing when you go into production. First, you want to have a test environment where you can test the proposed change and when you are done with it, go into production.
Bart Farrell: So missing readiness checks usually show up through something concrete. Traffic reaches a pod too early, auto-scaling behaves strangely, or users report errors. If a team wanted to catch this before users do, where would you have them look first?
Max Majander: I would tackle this challenge at the starting point. This is a point where you never want to end up. What I would do is create an internal policy where you can use tools like a validating webhook to avoid this challenge from the start.
Bart Farrell: Production readiness reviews can happen before launch, after incidents, during audits or not formally at all. What would you put in place so Kubernetes readiness gets reviewed before it becomes urgent?
Max Majander: Create a checklist. Make a list of things that need to be done and create an internal process to beat this challenge.
