fix(capi): keys for kubeadm-bootstrap controller #338
Merged
Conversation
This file contains 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
✅ Deploy Preview for kamaji-documentation canceled.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This hotfix is required for the Cluster API implementation, especially clastix/cluster-api-control-plane-provider-kamaji#39.
With the introduced changes, Kamaji will be responsible to create the Certificate Authority Secret required by Cluster API (e.g.
${TENANT_NAME}-ca) along with the expected keys, such astls.crtandtls.key.The rationale behind this is due to the CAPI Kubeadm bootstrap controller.
No breaking changes are expected for already deployed clusters.