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

Ignore --bootstrap-kubeconfig flag when config file already present #598

Closed
shivi28 opened this issue Jun 16, 2022 · 0 comments · Fixed by #606
Closed

Ignore --bootstrap-kubeconfig flag when config file already present #598

shivi28 opened this issue Jun 16, 2022 · 0 comments · Fixed by #606
Assignees
Milestone

Comments

@shivi28
Copy link
Contributor

shivi28 commented Jun 16, 2022

What steps did you take and what happened:

When we restart byo host agent, and if we passed --bootstrap-kubeconfig flag during the restart, then our controller fails with error message:
Screenshot 2022-06-15 at 5 14 20 PM

This happens because when we pass --bootstrap-kubeconfig flag again, then it generates the new CSR which is validated against old private key, which throws compatibility issue

What did you expect to happen:
To avoid this issue, we should ignore the --bootstrap-kubeconfig flag if config is already present in its path.

Environment:

  • Cluster-api-provider-bringyourownhost version:
  • Kubernetes version: (use kubectl version --short):
  • OS (e.g. from /etc/os-release):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants