Apply precaution when handling kube-system namespace
sfxworks opened this issue · comments
kubectl prune configmap --all-namespaces --dry-run=client
configmap/object-bucket-claim deleted (dry run)
configmap/helm-operator-kube-config deleted (dry run)
configmap/skyblock deleted (dry run)
configmap/cluster-info deleted (dry run)
configmap/cert-manager-cainjector-leader-election deleted (dry run)
configmap/cert-manager-cainjector-leader-election-core deleted (dry run)
configmap/cert-manager-controller deleted (dry run)
configmap/extension-apiserver-authentication deleted (dry run)
configmap/kubeadm-config deleted (dry run)
configmap/kubelet-config-1.18 deleted (dry run)
configmap/linkerd-config-addons deleted (dry run)
configmap/bungee-op-lock deleted (dry run)
configmap/nslock-op-lock deleted (dry run)
configmap/object-bucket-claim deleted (dry run)
configmap/server-op-lock deleted (dry run)
configmap/sftp-op-lock deleted (dry run)
configmap/config deleted (dry run)
configmap/prom-operator-grafana-test deleted (dry run)
configmap/prom-operator-prometheus-o-apiserver deleted (dry run)
configmap/prom-operator-prometheus-o-cluster-total deleted (dry run)
configmap/prom-operator-prometheus-o-controller-manager deleted (dry run)
configmap/prom-operator-prometheus-o-etcd deleted (dry run)
configmap/prom-operator-prometheus-o-grafana-datasource deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-coredns deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-cluster deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-namespace deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-node deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-pod deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-workload deleted (dry run)
configmap/prom-operator-prometheus-o-k8s-resources-workloads-namespace deleted (dry run)
configmap/prom-operator-prometheus-o-kubelet deleted (dry run)
configmap/prom-operator-prometheus-o-namespace-by-pod deleted (dry run)
configmap/prom-operator-prometheus-o-namespace-by-workload deleted (dry run)
configmap/prom-operator-prometheus-o-node-cluster-rsrc-use deleted (dry run)
configmap/prom-operator-prometheus-o-node-rsrc-use deleted (dry run)
configmap/prom-operator-prometheus-o-nodes deleted (dry run)
configmap/prom-operator-prometheus-o-persistentvolumesusage deleted (dry run)
configmap/prom-operator-prometheus-o-pod-total deleted (dry run)
configmap/prom-operator-prometheus-o-prometheus deleted (dry run)
configmap/prom-operator-prometheus-o-proxy deleted (dry run)
configmap/prom-operator-prometheus-o-scheduler deleted (dry run)
configmap/prom-operator-prometheus-o-statefulset deleted (dry run)
configmap/prom-operator-prometheus-o-workload-total deleted (dry run)
configmap/ingress-controller-leader-nginx deleted (dry run)
configmap/nginx-nginx-ingress-tcp deleted (dry run)
configmap/ceph-delete-bucket deleted (dry run)
configmap/object-bucket-claim deleted (dry run)
configmap/local-device-amd1 deleted (dry run)
configmap/local-device-amd2 deleted (dry run)
configmap/local-device-s1 deleted (dry run)
configmap/local-device-s2 deleted (dry run)
configmap/local-device-s3 deleted (dry run)
configmap/rook-ceph-operator-config deleted (dry run)
configmap/rook-ceph-pdbstatemap deleted (dry run)
Ran it as a test. Looks useful and I know that this is the purpose of dry-run. Though I'd say when using --all-namespaces some kube-system default config maps should be ignored least. Specifically:
configmap/kubeadm-config deleted (dry run)
configmap/kubelet-config-1.18 deleted (dry run)
