Kubernetes TopologySpread Cleanup: Fix Placement Rules After Clusters Change

Kubernetes topology spread cleanup starts when old zone, hostname, or pool assumptions keep shaping placement after the cluster has changed. A constraint that once protected availability can become a scheduler trap after nodes move, labels change, or a service no longer needs multi-zone spread.

For stale topology spread constraints, the useful cleanup output is a placement decision that names the workload, the current topology keys, the minimum availability requirement, and the scheduler behavior to watch after the change. Do not treat the constraint as waste because it is old. Prove whether it still prevents replica concentration, or whether it now blocks scheduling because the cluster no longer has the shape the manifest expects.

Key takeaways

Review stale topology spread constraints through topology keys, replica counts, pending events, node labels, and availability expectations.
Use a window that includes deployments, node rotations, and autoscaler events before deciding that placement rules are obsolete.
Start with the reversible move: shadow a narrower spread rule in a non-critical workload or one namespace first.
Slow down when concentrating replicas or blocking scheduling because old topology assumptions survived is still plausible.
Prevent repeat cleanup by making placement rules declare the topology key, reason, owner, and review trigger.

Map the Placement Assumption

Start with one deployment family where replicas, node labels, topology keys, and availability goals can be reviewed together. The best cleanup scope is small enough to test safely but wide enough to include anti-affinity, PDBs, node selectors, and autoscaler behavior that changes scheduling outcomes.

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	recent scheduling events, rollout history, node label changes, and zone/pool membership
Dependency evidence	deployment manifests, PDBs, autoscaler settings, topology keys, and incident notes
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.

Placement 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 topology spread cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Topology key reality	Current node labels for zone, hostname, pool, capacity type, and custom domains	The key no longer exists or maps to a different failure boundary
Scheduler pressure	Pending pods, unschedulable events, skew errors, and rollout stalls	The spread rule blocks placement more than it protects availability
Replica and PDB fit	Replica count, maxSkew, whenUnsatisfiable, and disruption budget	The rule expects more schedulable domains than the workload actually has
Availability history	Incidents, failovers, SLO notes, and customer impact during node loss	The spread rule still protects a known recovery requirement

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 this as a quick read-only scan, then compare current topology keys with the keys named in manifests before changing constraints.

kubectl get nodes -L topology.kubernetes.io/zone,kubernetes.io/hostname
kubectl get deploy -A -o jsonpath='{range .items[*]}{.metadata.namespace}/{.metadata.name}{"\n"}{.spec.template.spec.topologySpreadConstraints}{"\n\n"}{end}'
kubectl get events -A --field-selector reason=FailedScheduling

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Stage Constraint Changes

Use the least permanent move that proves the decision. In Kubernetes topology spread 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.

Change one workload or namespace before editing a shared chart default.
Replace an impossible key before deleting the entire constraint.
Watch pending pods, skew, rollout duration, and node pressure through the next deploy.

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.

Placement Rules That Need Patience

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Services that use topology spread as their only zone-failure protection.
Workloads with low replica counts where one unavailable domain changes skew math.
Platform chart defaults consumed by teams that do not own the shared template.

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 Placement Review

Run Kubernetes topology spread 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 a placement cleanup record with topology key, before/after skew, scheduler events, owner approval, and rollback patch.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. Use the main cloud cost checklist to decide whether the cleanup work has enough upside for a focused sprint. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Keep Placement Rules Current

Prevention should change the creation path, not just the cleanup path. For Kubernetes topology spread cleanup, the useful prevention fields are owner labels, expiry annotations, resource quotas, and regular namespace review. Make those fields part of normal creation and review.

Require every spread rule to name the failure domain it protects.
Review topology keys after cluster migrations, node-pool splits, and region changes.
Keep shared Helm defaults separate from workload-specific placement requirements.

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 topology spread constraints in Kubernetes clusters, node pools, availability zones, and workload scheduling rules
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Topology key reality, scheduler pressure, and owner confirmation
First reversible move	Patch one low-risk workload or namespace before editing shared defaults
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 batch schedules, traffic peaks, and deployment cycles
Prevention rule	Require topology key, protected failure domain, owner, and review trigger

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 topology spread cleanup?

Use a window long enough to include batch schedules, traffic peaks, and deployment cycles 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, right-size requests and limits before removing capacity when workloads still matter. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to cronjobs, batch workloads, and month-end processing that make average utilization misleading. 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.