Inventory of containerised workloads and clusters
Most teams cannot say on demand how many clusters they run, which Kubernetes version each is on, or which images in production were built from a Dockerfile nobody has opened in two years. A single inventory of clusters, namespaces, workloads and their image sources turns guesswork into a list you can prioritise from.
First tasks
- List every cluster and kubeconfig context you can reach in a shared sheet
- Export deployments, statefulsets and daemonsets with their images from each cluster
- Look up the end of support date for each cluster's Kubernetes version
- Mark workloads using public images or the latest tag
- Write the five most worrying findings at the top of the sheet