-
Notifications
You must be signed in to change notification settings - Fork 335
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
Test orc2 #5452
base: main
Are you sure you want to change the base?
Test orc2 #5452
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MaysaMacedo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
23a2165
to
80cba4d
Compare
@@ -162,6 +162,9 @@ func reconcileOpenStackImageSpec(hcluster *hyperv1.HostedCluster, openStackImage | |||
}, | |||
}, | |||
} | |||
if hcluster.Annotations[hyperv1.CleanupOrcImageResourcesAnnotation] == "false" { | |||
openStackImageSpec.ManagedOptions.OnDelete = "detach" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should use the type from ORC if it's possible.
Instead of forcing the users to provide an existing OpenStack Glance image, we now let our CAPI provider to upload the image used in the release payload and handle its lifecycle with ORC.
This commit updates the openstack image name to contain the release image version.
The ORC objects should be created in the same namespace as the CAPO deployment, otherwise CAPO won't see any ORC object to handle.
This commit updates the ownerReference of the ORC Image to point to the openstack Cluster object. This is necessary because the resource that the ORC Image depends on should be in the same namespace as the ORC Image object.
80cba4d
to
716ea4c
Compare
716ea4c
to
6cc6657
Compare
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist