Quantum-Ready Kubernetes: How Do We Get There?
summary
By 2035 US procurement requires quantum-safe solutions and NIST already standardized first post‑quantum algorithms last August, so Kubernetes stacks need concrete changes: upgrade to TLS 1.3, add crypto inventory via seabbombs, and implement crypto agility so keys and algorithms are replaceable. Real tools exist—KisKit and OpenSSL 3.5 patches—and real workloads show value (CERN validates quantum beam‑calibration on a live proton beam). Major gaps are hybrid orchestration, nonstandard quantum billing/units, and extreme device scarcity; portability and testing now avoid painful rewrites later.
AI-written summary · about
chapters (26)
- 0:00Quantum and Kubernetes intro
- 1:05Panelist backgrounds
- 2:28Quantum hype vs reality
- 3:31CERN quantum initiatives
- 4:13Post-quantum crypto standards
- 6:00Kubernetes crypto changes
- 8:06Post-quantum crypto projects
- 9:08Quantum toolkits and education
- 10:09Migrating clusters quantum-safe
- 12:16Quantum workloads on K8s
- 13:39Quantum ML at CERN
- 15:04K8s role in quantum cloud
- 16:30Hybrid quantum future
- 17:14Start quantum machine learning
- 18:37Quantum algorithms learning
- 20:24Next steps for professionals
- 21:06Steps for maintainers
- 22:31Encourage quantum contributors
- 23:15Quantum procurement challenges
- 24:19CNCF quantum forum needed
- 25:01Lessons from AI for quantum
- 26:26Post-quantum crypto efforts
- 27:08CNCF quantum proposal
- 27:30Key takeaways
- 28:11Q&A quantum workloads
- 31:25Quantum ethics considerations
related talks
05mLightning Talk: Building Quantum-Safe Applications
30mNavigating the Quantum Readiness Journey: Securing Kubernetes with Quantum-Resis...
38mA Quantum Computing Talk Without Qubits
15mSecuring Cloud Native Infra for the Post-Quantum Era
48mPreparing for Quantum: A Pragmatic Approach towards Readiness
20mCryptographic Resilience in the Quantum Era
05mPost-Quantum DevOps
21mCybersecurity in the Age of Quantum