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

Replacing controller node on bare-metal platform does not re-join etcd member #446

Open
invidian opened this issue May 19, 2020 · 1 comment
Open

Replacing controller node on bare-metal platform does not re-join etcd member #446

invidian opened this issue May 19, 2020 · 1 comment
Labels
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

Currently our bare-metal ignition configuration for controller lacks etcd-rejoin script, which means if the bare-metal controller node gets replaced, it won't automatically join etcd 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 labels May 19, 2020
@invidian invidian mentioned this issue May 19, 2020
Open
@invidian invidian mentioned this issue Feb 18, 2021
Merged
@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.
Assignees
No one assigned
Labels
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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@invidian