supraj.dev Search

Kubernetes / REFERENCE BLUEPRINT

K8s Deprecation Radar

Cluster upgrades slip because nobody knows what will break. This loop answers that question the day a new minor goes GA — per team, per manifest, with the exact patch — so the upgrade window is a decision, not an investigation.

Explore the workflowCheck prerequisites
DESIGN INTENT

This is documentation for a proposed implementation. No automation runs from this page. Commands, configuration, output and timing are illustrative; package availability and measured performance have not been verified here.

THE LOOP / 4 STEPS

From the first signal to the final action.

  1. 01

    TRIGGER

    EKS/GKE release feed: new minor GA

  2. 02

    SCAN

    live API usage per cluster vs removed/deprecated list

  3. 03

    MAP

    offending manifests → owning team via CODEOWNERS

  4. 04

    ACT

    one GitHub issue per team with exact manifest patches

01 / USAGE

How the intended workflow fits together

  1. 01

    Watches the EKS/GKE release feeds. On GA of a new minor, it diffs the deprecated-API list against 30 days of audit-log usage — not just manifests, actual calls.

  2. 02

    Each offending resource is traced to its owning team through CODEOWNERS, so nobody gets a 400-line shared spreadsheet.

  3. 03

    Issues include the exact apiVersion patch and a working kubectl-convert command. Close the issues, schedule the upgrade.

02 / CONFIGURATION

Read the configuration contract

Point it at your kube contexts and repo. No AI step here — this loop is fully deterministic.

Illustrative configuration. Adapt only after verifying the implementation, schema and service permissions.

# radar.yaml
trigger:
  feed: eks-release-notes
scan:
  contexts: [prod-eks, staging-eks, dev-eks]
  source: audit-log:30d   # what's actually called
map:
  owners: CODEOWNERS
act:
  issues: acme/platform
  label: k8s-upgrade

03 / EVIDENCE

What an output could look like

This authored example describes the intended result format. It is not evidence that a live run occurred.

$ dep-radar report --minor 1.34
cluster prod-eks: 7 deprecated usages
  team payments  → 3 (Ingress v1beta1)
  team ml-infra  → 4 (PodDisruptionBudget v1beta1)
issues filed: 2 · est. effort: ~1h each
clusters staging, dev: clean ✓

04 / IMPLEMENTATION REFERENCE

Review the setup sketch

The original command sketch is preserved for design context. It is not a verified installation recipe. Confirm that the package or repository exists and review its implementation before running anything.

Show illustrative setup commands
brew install supraj/tap/dep-radar
dep-radar init --contexts prod-eks,staging-eks,dev-eks