Container Runtime Class Cleanup: Remove Sandboxed Runtime Exceptions After Workloads Move

Kubernetes RuntimeClass cleanup starts when sandboxed runtimes, Kata-style isolation, or dedicated runtime handlers remain after sensitive workloads move. The class may have no obvious pods today, but admission policies, Helm defaults, and rollback manifests can still point at it.

For stale RuntimeClasses and sandboxed runtime exceptions, cleanup should connect pods using runtimeClassName, node runtime support, admission exceptions, security owners, and rollback capacity. The useful output is a RuntimeClass retirement record with handler name, workload evidence, node support, policy references, replacement runtime, and rollback manifest: Move workloads to the replacement runtime and canary scheduling before removing the class.

Key takeaways

• Review stale RuntimeClasses and sandboxed runtime exceptions through runtimeClassName use, Node handler support, Admission references, not age alone.
• Use one workload rollout cycle plus batch, security-review, and rollback windows before deciding that quiet means unused.
• Start with the reversible move: move workloads to the replacement runtime and canary scheduling before removing the class.
• Slow down when scheduling workloads onto unsupported runtimes or deleting isolation paths before callers move is still plausible.
• Prevent repeat cleanup by making teams create RuntimeClasses with owner, handler, isolation reason, allowed namespaces, and retirement trigger.

Map Runtime Handlers

Start with one cluster or node pool family where RuntimeClasses, pod specs, admission policies, and node runtime handlers can be reviewed together. The best cleanup scope is small enough that owners can answer quickly but wide enough to include rollback manifests and security exceptions.

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	pods with runtimeClassName, pending scheduling events, node handler support, and rollout history
Dependency evidence	workload manifests, admission policies, Helm values, security review, and node runtime config
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.

RuntimeClass Evidence

The useful question is not “how old is it?” It is “what would fail to schedule, lose isolation, or bypass policy if this disappeared?” For Kubernetes RuntimeClass cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Pod usage	Pods, Jobs, CronJobs, and templates with runtimeClassName	No supported workload still requests the class
Node handler support	Runtime handler names, node labels, taints, and scheduling events	Nodes no longer need the old sandboxed runtime
Admission references	PodSecurity exceptions, policy engines, namespace allowlists, and Helm values	No policy still assumes the class exists
Rollback path	Replacement RuntimeClass, canary pod, workload owner, and rollback manifest	Workloads can move without losing isolation guarantees

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

Use read-only cluster checks to find the class, then compare live pods with manifests before changing scheduling policy.

kubectl get runtimeclass
kubectl get pods --all-namespaces -o jsonpath='{range .items[?(@.spec.runtimeClassName)]}{.metadata.namespace}{" "}{.metadata.name}{" "}{.spec.runtimeClassName}{"\n"}{end}'
kubectl get events --all-namespaces --field-selector reason=FailedScheduling
rg "runtimeClassName|RuntimeClass" k8s helm deploy

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.

Canary Scheduling Before Removal

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

• Move workloads to the replacement runtime and canary scheduling before removing the class.
• Remove admission exceptions only after workloads schedule and pass security checks without the old handler.
• Keep node runtime rollback notes until the next rollout proves the replacement path.

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.

Cases That Need a Slower Path

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

• Security-sensitive workloads that used sandboxing for tenant isolation or untrusted code.
• Batch Jobs and CronJobs that may not create pods during a short observation window.
• Admission policies, Helm charts, or rollback manifests that default to the old handler.

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

Run Kubernetes RuntimeClass cleanup as a decision review, not an open-ended hygiene project.

1. Pick the narrow scope and export the candidate list.
2. Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
3. Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
4. Apply the least permanent useful change first.
5. Watch the signals that would reveal a bad decision.
6. Complete the final removal only after the review window closes.
7. Save a RuntimeClass retirement record with handler name, workload evidence, node support, policy references, replacement runtime, and rollback manifest.

For broader cleanup planning, use the cleanup library to pair this guide with related notes.

Prevent the Repeat

Prevention should change the creation path, not just the cleanup path. For Kubernetes RuntimeClass 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.

• Create RuntimeClasses with owner, handler, isolation reason, allowed namespaces, and retirement trigger.
• Review runtime handlers when node images, sandboxing tools, or admission policies change.
• Keep RuntimeClass use in workload manifests rather than hidden in copied Helm defaults.

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 RuntimeClasses and sandboxed runtime exceptions in Kubernetes clusters, workload manifests, node pools, admission policies, security profiles, and platform ownership records
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Workload demand, Namespace ownership, and owner confirmation
First reversible move	Right-size requests and limits before removing capacity when workloads still matter
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 owner labels, expiry annotations, and resource quotas for temporary namespaces

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 RuntimeClass 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.