Bart Farrell: First, who are you, what's your role, and where do you work?
Olli Tuominen: Hey, my name is Olli Tuominen. I'm from SUSE. I'm working as a solution architect.
Bart Farrell: A Kubernetes setting can look wrong but still feel risky to change once it's already in production. Requests, limits, autoscaling, or probe. What would you tell a team that sees the problem but is nervous the fix could cause an outage?
Olli Tuominen: Use our AI crew. That helps you or the team to analyze the issue. what we have implemented here is also the possibility to use MCP, LLM, to ask the question why it has been failing, and then what are the remediation for that service.
Bart Farrell: Missing readiness checks usually shows 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?
Olli Tuominen: Our observability provides the insight of every traffic from the log metrics and traces, so you could see all that the traffic, how it flows, what are the issues inside the pods. user observability definitely helps on that.
Bart Farrell: We're here at KCD Helsinki. We're hearing a lot about AI and Kubernetes. Where do you think it's a good idea to use AI and where would you say probably not yet ready?
Olli Tuominen: AI is a hot topic today's Kubernetes environment but we provide this safe place to run your own environment AIs. But also what we provide with the SUSE Rancher is also that SRE2 for the AI to help you to mitigate issues in the production with the AI. It includes the human in the loop so it doesn't do of bad things before it enters the projects.
