Skip to main content
Link
Menu
Expand
(external link)
Document
Search
Copy
Copied
k8s-aibom
Overview
Installing on EKS, AKS, and other conformant clusters
Compatibility & Support
Incident response: “where is X running?”
Policy Cookbook: acting on AIBOM facts
Security model
Design documents
Design 001: API graduation to v1beta1
Design 002: Sigstore/Rekor verifier — the verified signature tier
Design 003: Native CRD scrapers — Dynamo, NIMService, LeaderWorkerSet
Design 004: Watch isolation for third-party kinds
Design 005: Ownership roll-up for CRD-owned workloads (+ CronJob, pod digests for CRD kinds)
Design 006: Configurable workload-kind allowlist
Design 007: llm-d lens — DisaggregatedSet coverage and InferencePool membership
Evidence
v1.5.1 on GKE: upgrade, rollback, and API-server cost — measured
v1.6.0-rc.1 on GKE: two-chart install, DisaggregatedSet roll-up, steady-state cost
v1.6.1 on GKE: ADR-019 requalification legs, with the Dynamo pairing
Integrations
Feeding BOMs to OWASP Dependency-Track
Building from Source
Contributing a detection pattern
External CRD version pinning
Merge criteria
Migrating to the v1beta1 API
Quality Baseline: v1.0 Release
Release Checklist
Roadmap
Schema divergences
Scraper heuristics
Threat model
Webhook sink protocol
k8s-aibom CycloneDX Property Taxonomy
Search k8s-aibom
GitHub
Releases
Integrations
How to feed k8s-aibom output into downstream tools and platforms.
Table of contents
Feeding BOMs to OWASP Dependency-Track