Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Shutting down bare-metal nodes do not remove them from the cluster #448

Open
invidian opened this issue May 19, 2020 · 1 comment
Open
Labels
area/feature-parity Ensuring things are similar on all platforms area/kubernetes Core Kubernetes stuff bug Something isn't working low-hanging-fruit Issues good for beginners platform/bare-metal Bare-metal-related

Comments

@invidian
Copy link
Member

On other platforms, we have /etc/kubernetes/delete-node which gets triggered, when kubelet service stops. This is missing on bare-metal, which may cause orphan nodes to stay around registered in the cluster.

@invidian invidian added bug Something isn't working area/kubernetes Core Kubernetes stuff low-hanging-fruit Issues good for beginners platform/bare-metal Bare-metal-related area/feature-parity Ensuring things are similar on all platforms labels May 19, 2020
@invidian
Copy link
Member Author

Might be resolved by #1374.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/feature-parity Ensuring things are similar on all platforms area/kubernetes Core Kubernetes stuff bug Something isn't working low-hanging-fruit Issues good for beginners platform/bare-metal Bare-metal-related
Projects
None yet
Development

No branches or pull requests

1 participant