Skip to content

Automatically clean up kubeadm backup files in /etc/kubernetes/tmp after cluster upgrade #13412

Description

@kiddingbaby

What would you like to be added

Add automatic cleanup of kubeadm etcd backups (/etc/kubernetes/tmp/kubeadm-backup-etcd-*) after cluster upgrade, with configurable retention policy (e.g., kubeadm_backup_retention_count).

root@node1:~# du -h --max-depth=1 /etc/kubernetes/tmp/ | sort -h
4.0K    /etc/kubernetes/tmp/kubeadm-backup-manifests-2026-08-10-13-09-29
4.0K    /etc/kubernetes/tmp/kubeadm-backup-manifests-2026-08-10-13-10-22
4.0K    /etc/kubernetes/tmp/kubeadm-backup-manifests-2026-08-10-14-39-37
4.0K    /etc/kubernetes/tmp/kubeadm-backup-manifests-2026-08-10-21-43-54
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-config-2026-08-10-13-09-52
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-config-2026-08-10-13-10-27
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-config-2026-08-10-14-39-53
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-config-2026-08-10-21-43-57
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-env2351038227
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-env3954931097
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-env4164549448
8.0K    /etc/kubernetes/tmp/kubeadm-kubelet-env4260571546
702M    /etc/kubernetes/tmp/kubeadm-backup-etcd-2026-08-10-13-09-29
702M    /etc/kubernetes/tmp/kubeadm-backup-etcd-2026-08-10-13-10-22
702M    /etc/kubernetes/tmp/kubeadm-backup-etcd-2026-08-10-14-39-37
702M    /etc/kubernetes/tmp/kubeadm-backup-etcd-2026-08-10-21-43-54
2.8G    /etc/kubernetes/tmp/

Why is this needed

These backups accumulate over multiple upgrades, consuming GBs of disk space and potentially filling root partition. Kubespray already has similar retention for etcd backups (#6836), but not for kubeadm-generated ones.

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions