Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-run certain kubeadm init phases after config changes #51

Open
RobReus opened this issue Jul 26, 2020 · 1 comment
Open

Re-run certain kubeadm init phases after config changes #51

RobReus opened this issue Jul 26, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request feature_request

Comments

@RobReus
Copy link
Member

RobReus commented Jul 26, 2020

Details

Describe the solution you'd like:

Right now, kubeadm init only runs whenever you setup a fresh cluster/node. Certain config changes to the kubeadm init config should trigger certain init phases to be ran again. For example, the upload-config phase which uploads the config to a configmap, or the phases which generate the static pod configuration manifests.

Anything else you would like to add:

Additional Information:

@RobReus RobReus added the enhancement New feature or request label Jul 26, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.85. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@RobReus RobReus self-assigned this Jul 26, 2020
@RobReus RobReus added this to To do in Raspbernetes Q3 via automation Jul 26, 2020
@xunholy xunholy moved this from To do to In progress in Raspbernetes Q3 Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature_request
Projects
Raspbernetes Q3
  
In progress
Development

No branches or pull requests

1 participant