How to eliminate availability risks and perform timely upgrades
summary
A SaaS platform called Check codifies real incidents into an availability risk signature database and a Knowledge Graph, scans upstream-compliant Kubernetes clusters with a lightweight read‑only cronjob, and generates actionable workflows. Three modules—Risk Ledger, Artifact Register and Upgrade co-pilot—claim to cut research/pre‑work 8x, upgrade execution 2x and overall upgrade cycles 3x, cover 200+ add‑ons, add missing add‑ons within 48 hours, and produce pre/post‑flight checks and remediation steps.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:08Kubernetes upgrade risks
- 4:14Learning from failures
- 7:47Check’s platform overview
- 8:29Risk Ledger for incidents
- 9:51Artifact Register for add-ons
- 10:13Upgrade Co-Pilot
- 11:37Collective learning technology
- 14:26Check integrations and dashboard
- 15:30Shared Kubernetes ops responsibility
- 16:56Private instances for enterprise
- 19:07Exact answers in upgrades
- 21:16Tracking and remediating risks
- 23:57Mitigation workflows
- 24:59Q&A
related talks
25mAutomating Kubernetes Upgrades for Zero Downtime
37mKubernetes Security and How to Fix K8s Cluster at Scale
05mUpgrading K8s: run as fast as we can, just to stay in place
10mGenesis Startup Competition Pitch
16mK8s, created for fast deployment, connectivity and ease of use
38mFrom Risks to Resilience: Leveraging CNCF Projects Against Kube...
11mSecuring the Kubernetes Ecosystem
30mSoftware Supply Chain Management with Grafeas and Kritis