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
baremetal: create machines and machineset linked to cluster #3935
baremetal: create machines and machineset linked to cluster #3935
Conversation
The installer takes the cluster name given by the user and appends a random string. MachineSets and Machines create within the cluster need to be linked to that cluster in order to be recognized by some of the controllers in the machine API. This is especially important, for example, when scaling a MachineSet to ensure that the new Machines created by the machine-set-controller are linked to the MachineSet properly. See https://bugzilla.redhat.com/show_bug.cgi?id=1857175 for more details. This change drops the use of cluster name in the MachineSet and Machine resoures created for a baremetal cluster and uses the clusterID instead. The baremetal platform was the only one using name instead of ID in this way. Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
/test images |
/test e2e-aws-fips |
/retest |
1 similar comment
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
The installer takes the cluster name given by the user and appends a
random string. MachineSets and Machines create within the cluster need
to be linked to that cluster in order to be recognized by some of the
controllers in the machine API. This is especially important, for
example, when scaling a MachineSet to ensure that the new Machines
created by the machine-set-controller are linked to the MachineSet
properly. See https://bugzilla.redhat.com/show_bug.cgi?id=1857175 for
more details.
This change drops the use of cluster name in the MachineSet and
Machine resoures created for a baremetal cluster and uses the
clusterID instead. The baremetal platform was the only one using name
instead of ID in this way.