-
Notifications
You must be signed in to change notification settings - Fork 28
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
Can not create Cluster from Cluster Class without repeating KCP's infrastructureRef #341
Labels
kind/bug
Something isn't working
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
anmazzotti
added
kind/bug
Something isn't working
needs-priority
Indicates an issue or PR needs a priority assigning to it
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 31, 2024
alexander-demicev
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-priority
Indicates an issue or PR needs a priority assigning to it
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 31, 2024
By briefly looking into our API and comparing it to CAPI's kubeadm, I observed the following divergance within our API:
|
This issue is stale because it has been open 90 days with no activity. |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Sep 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Something isn't working
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What happened:
When defining my RKE2 cluster class I configured the
RKE2ControlPlaneTemplate
as follows:In the CC definition the
spec.controlPlane.machineInfrastructure.ref
is correctly set:However RKE2 provider fails to initialize the control plane machines:
The workaround is to repeat the
infrastructureRef
in theRKE2ControlPlaneTemplate
, like this:I think this should not be necessary due to the CC definition.
What did you expect to happen:
The RKE2ControlPlaneTemplate should respect what was defined in the Cluster Class.
How to reproduce it:
See config above, or it can be reproduced with the quickstart sample by removing the
RKE2ControlPlaneTemplate.spec.template.spec.infrastructureRef
object. referenceAnything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
/etc/os-release
):The text was updated successfully, but these errors were encountered: