Skip to content

kata-deploy: remove containerd handlers a redeploy drops - #13810

Draft
fidencio wants to merge 2 commits into
kata-containers:mainfrom
fidencio:topic/kata-deploy-prune-stale-containerd-handlers
Draft

kata-deploy: remove containerd handlers a redeploy drops#13810
fidencio wants to merge 2 commits into
kata-containers:mainfrom
fidencio:topic/kata-deploy-prune-stale-containerd-handlers

Conversation

@fidencio

@fidencio fidencio commented Sep 9, 2026

Copy link
Copy Markdown
Member

configure_containerd only ever added handlers, so turning a variant off left its stanza behind naming the configuration the same redeploy had deleted. The node kept advertising the handler and pods on it hung in ContainerCreating.

Reconcile instead: drop every stanza under this installation's dest_dir that the current configuration did not just write, and its
runtime_platforms entry in the CRI images plugin.

configure_containerd only ever added handlers, so turning a variant off
left its stanza behind naming the configuration the same redeploy had
deleted. The node kept advertising the handler and pods on it hung in
ContainerCreating.

Reconcile instead: drop every stanza under this installation's dest_dir
that the current configuration did not just write, and its
runtime_platforms entry in the CRI images plugin.

Assisted-by: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
Toggle debug off against a live cluster and assert the handler leaves the
containerd configuration and node.status.runtimeHandlers with its
RuntimeClass, while the base shim keeps running pods.

Assisted-by: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant