r/kubernetes • u/anish2good • 16h ago
How a Kubernetes StatefulSet Keeps Its Storage — manic
Enable HLS to view with audio, or disable this notification
r/kubernetes • u/anish2good • 16h ago
Enable HLS to view with audio, or disable this notification
r/kubernetes • u/Suspicious_Orchid770 • 19h ago
We ran into this evaluating inference frameworks for a production LLM workload: clean benchmarks hid exactly the failure modes that matter at the infra layer.
Bursty concurrency and mixed prompt lengths exposed GPU memory pressure and latency spikes that never showed up under steady synthetic load.
We ended up building a testing process around soak tests and simulated failure scenarios (node loss, sudden load spikes) instead of trusting a single throughput number. Wrote up what we found and the process we now use before committing to a framework.
r/kubernetes • u/Parking_Range9163 • 5h ago
I am a pentester, mostly web apps and internal networks. I'm currently learning Kubernetes, and one thing keeps bothering me. In K8s, I see scanning everywhere through kube-bench, Trivy, Falco, and admission policies; however, nothing about actually testing these guardrails.
How are people validating that these actually fire? Is it through manual attempts, or is there tooling I've missed?
r/kubernetes • u/AutoModerator • 22h ago
Share any new Kubernetes tools, UIs, or related projects!
r/kubernetes • u/kubernetespodcast • 15h ago
https://kubernetespodcast.com/episode/269-ai-usage/
Check out our latest episode: Navigating AI Policies in Kubernetes, with Kat Cosgrove and Natali Vlatko!
When people talk about AI in Kubernetes, the conversation is often focused on the user side, but for open source maintainers, there's of course a lot to unpack on how AI is changing oss contribution! How does AI impact the community, and what are the new rules of engagement?
We sat down with Kat Cosgrove (SIG Docs Technical Lead, SIG Release Subproject Lead, and Kubernetes Steering Committee member) and Natali Vlatko (SIG Docs Co-Chair, TODO Group Steering Committee member, and OSPO at Cisco) to unpack the recently published Kubernetes AI usage policy for contributors.
Topics covered include:
- Why you can't call an AI tool your "co-author" for legal reasons (because the AI tool can't sign the CLA)
- The rise of "AI slop" PRs and why AI-generated comments are causing trouble for OSS maintainers & reviewers.
- And of course, paths for new contributors to get involved sustainably!
Tune in for an insider's perspective into how AI is impacting contribution to one of the world's largest OSS projects!