Security
Kubernetes Registry Credential Cleanup: Remove Pull Secrets After Workload Identity Moves
Kubernetes registry credential cleanup starts after clusters move from copied pull secrets to workload identity, node identity, or registry-specific federation. The risky leftovers are imagePullSecrets, Docker config secrets, old registry service accounts, and namespace annotations that still let pods authenticate with credentials nobody rotates. They can look harmless until a deployment, rollback, or private base image still depends on them.
For stale registry pull secrets and image credentials, the review has to connect risk acceptance, reachability, compensating controls, and the current owner. The useful output is an access cleanup record with caller map, scope change, staged disable date, rollback owner, and final revocation: Rotate or narrow scope before deleting the old credential, identity, certificate, or rule, keep proof of the security decision, and avoid letting breaking image pulls or leaving retired registry credentials available in namespaces become the hidden default.
Key takeaways
- Review stale registry pull secrets and image credentials through Last legitimate use, Caller inventory, Scope and exposure, not age alone.
- Use a window long enough to include deploys, scheduled jobs, client renewals, vendor callbacks, and incident workflows before deciding that quiet means unused.
- Start with the reversible move: rotate or narrow scope before deleting the old credential, identity, certificate, or rule.
- Slow down when breaking image pulls or leaving retired registry credentials available in namespaces is still plausible.
- Prevent repeat cleanup by making teams require owner, purpose, scope, expiry, and rotation path when access is created.
Map Pull Secret Usage
Start with one namespace group, registry hostname, or deployment family where callers and owners can be reviewed together. Include pod specs, service accounts, Helm values, admission policies, image references, CI deploy jobs, and registry audit logs so the team can distinguish unused credentials from credentials that are still the only path to a private image.
| Field | Why it matters |
|---|---|
| Owner | Cleanup needs a person or team that can accept the decision |
| Current purpose | A short reason to keep the item, written in present tense |
| Last meaningful use | Last pod pull, rollout, rollback, or CI deploy that referenced the secret |
| Dependency evidence | Pod specs, service accounts, Helm values, registry audit logs, and deploy jobs |
| Risk if wrong | The outage, data loss, access failure, or rollback gap the review must avoid |
| Next action | Keep, reduce, archive, disable, remove, or investigate |
Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.
Image Pull Evidence to Trust
The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For Kubernetes registry credential cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Secret references | imagePullSecrets, service account defaults, Helm values, Kustomize patches, and admission mutations | No live or generated manifest still names the secret |
| Registry audit trail | Pull events, denied pulls, token use, and repository scope for the credential | Pulls have moved to the new workload identity path |
| Rollback images | Old release digests, private base images, and emergency rollback manifests | Supported rollback paths no longer require the copied secret |
| Namespace exposure | Secrets copied across namespaces, broad repository grants, and unrotated Docker config JSON | The credential is broader or older than any current need |
Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.
If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.
Example Evidence Check
Use a read-only cluster scan to find where pull secrets are still attached. Compare the output with registry audit logs before disabling any credential.
kubectl get serviceaccount --all-namespaces -o jsonpath='{range .items[*]}{.metadata.namespace}{" "}{.metadata.name}{" "}{.imagePullSecrets[*].name}{"\n"}{end}'
kubectl get pods --all-namespaces -o jsonpath='{range .items[*]}{.metadata.namespace}{" "}{.metadata.name}{" "}{.spec.imagePullSecrets[*].name}{"\n"}{end}'
kubectl get secrets --all-namespaces -o jsonpath='{range .items[?(@.type=="kubernetes.io/dockerconfigjson")]}{.metadata.namespace}{" "}{.metadata.name}{"\n"}{end}'Treat the output as a candidate list. It proves references, not safety: a secret with no live pod reference may still appear in Git, a rollback manifest, or an admission webhook.
Rotate Before You Revoke
Use the least permanent move that proves the decision. In Kubernetes registry credential cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.
- Rotate or narrow scope before deleting the old credential, identity, certificate, or rule.
- Disable one caller path at a time and watch audit logs before final removal.
- Remove copied secrets, renewal jobs, allowlists, docs, and owner records after the cutover is complete.
Track the cleanup candidate with a simple priority score:
| Score | Good sign | Bad sign |
|---|---|---|
| Impact | Meaningful spend, risk, toil, noise, or confusion disappears | The item is cheap and low-risk but politically distracting |
| Confidence | Owner, purpose, and dependency path are understood | The team is guessing from age or name |
| Reversibility | Restore, recreate, re-enable, or rollback path exists | Deletion would be the first real test |
| Prevention | A rule can stop recurrence | The same pattern will return next month |
Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.
Pull Secrets That Need Patience
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- Deploy automation, break-glass access, payment integrations, old mobile clients, and vendor callbacks.
- Certificates or keys embedded in systems that do not report clean last-use data.
- Nested identity groups, inherited roles, and allowlists shared by several services.
For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.
Run the Credential Review
Run Kubernetes registry credential cleanup as a decision review, not an open-ended hygiene project.
- Pick the narrow scope and export the candidate list.
- Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
- Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
- Apply the least permanent useful change first.
- Watch the signals that would reveal a bad decision.
- Complete the final removal only after the review window closes.
- Save an access cleanup record with caller map, scope change, staged disable date, rollback owner, and final revocation.
For broader cleanup planning, use the cleanup library to pair this guide with related notes that match the same cleanup risk.
Stop Secret Copies Returning
Prevention should change the creation path, not just the cleanup path. For Kubernetes registry credential cleanup, the useful prevention fields are owner, expiry date, least-privilege scope, rotation schedule, and removal notes. Make those fields part of normal creation and review.
- Require owner, purpose, scope, expiry, and rotation path when access is created.
- Prefer short-lived credentials and managed identity flows where the platform supports them.
- Review stale access with caller evidence, not only age or naming conventions.
The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.
Example Decision Record
Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.
| Field | Example entry for this cleanup |
|---|---|
| Candidate | Stale registry pull secrets and image credentials in Kubernetes namespaces, private registries, workload identities, and deployment pipelines |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Last legitimate use, Caller inventory, and owner confirmation |
| First reversible move | Rotate or narrow scope before deleting the old credential, identity, certificate, or rule |
| Watch signal | The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong |
| Final action | Keep, reduce, archive, disable, or remove after a window long enough to include deploys, scheduled jobs, client renewals, vendor callbacks, and incident workflows |
| Prevention rule | Require owner, purpose, scope, expiry, and rotation path when access is created |
This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.
FAQ
How often should teams do Kubernetes registry credential cleanup?
Use a window long enough to include deploys, scheduled jobs, client renewals, vendor callbacks, and incident workflows for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.
What is the safest first action?
The safest first action is usually ownership repair plus evidence collection. After that, rotate or narrow scope before deleting the old credential, identity, certificate, or rule. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to deploy automation, break-glass access, payment integrations, old mobile clients, and vendor callbacks. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.
How do you make the decision useful later?
Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.