-
Notifications
You must be signed in to change notification settings - Fork 227
Ensure the Baremetal CRD is installed before metal3 is deployed #398
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
Conversation
a9372a5 to
59eed14
Compare
|
/test e2e-aws-operator |
|
/retest |
|
/test e2e-aws-scaleup-rhel7 |
|
/test e2e-aws-operator |
1 similar comment
|
/test e2e-aws-operator |
|
/test e2e-aws |
|
/test e2e-aws-upgrade |
|
/test e2e-aws-operator |
Moving install of the baremetal CRD to before 0000_30_machine-api-operator_11_deployment.yaml so that it is available at the time of Metal3 deployment. Fixes issue openshift#397.
|
/test e2e-aws-upgrade |
|
/test e2e-aws-scaleup-rhel7 |
|
@bison @ingvagabund can you please provide your reviews? |
|
can you please update the description and the commit message? the |
|
@sadasu ignore my comment above, I haven't notice the install/ file move |
|
/lgtm |
|
@michaelgugino would you be able to review this? |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre, michaelgugino 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 |
Moving installation of Baremetal CRD before Metal3 deployment happens.
Also, adding the baremetal CRD to kustomization.yaml to keep it up-to-date.
Fixes issue #397.