Chkk's Collective Learning technology mines and curates known errors, failures, and disruptions that the Kubernetes community (comprising users/operators, cloud providers, and vendors) has encountered, ensuring that past mistakes are not repeated.
Availability Risk Signature Database (ARSig DB) is the heart of Collective Learning–think of it as a CVE database for Availability Risks. Our technology continuously mines and populates this database using information from publicly available information: incidents, reports, tickets, issues, and internet forums. Chkk users can also opt-in to share this information with us. We scour everywhere that we can find a signal. This signal is codified as a programmatic signature that is later scanned and contextualized in our customers’ Kubernetes infrastructures.
Knowledge Graph learns of changes happening across hundreds of open-source projects and add-ons in the Kubernetes ecosystem to model their impact and determine the safest upgrade paths. Detectors track thousands of open-source and vendor container images, deployment/packaging tools, configurations, and dependencies to catalog what’s running in a Kubernetes fleet and where it’s running. Detectors help locate and localize what you are running so you can fix risks once and then keep them fixed.
The Chkk Research Team reviews and curates Availability Risk Signatures before they are published to the ARSigDB. This helps make Availability Risks actionable, ensuring that you are not inundated with unnecessary alerts and allows your team to focus on the most critical Availability Risks at any given point in time.
