This repository was archived by the owner on Mar 2, 2022. It is now read-only.
[WIP] Leverage kubeadm to bootstrap a secure etcd cluster #182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating this draft PR to get some eyes on this.
In the current state, we are creating a systemd drop-in to get the kubelet into a working state so that it starts up the etcd static pods. The problem is that this drop-in overrides the kubeadm drop-in, which results in kubeadm being unable to properly configure the kubelet at
kubeadm inittime.One thing I was experimenting with is removing the drop-in once the etcd cluster is up, but this feels bad.