Skip to content
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

Patch the CSV to handle breaking change for peer-pods #455

Open
wants to merge 3 commits into
base: release-1.7
Choose a base branch
from

Conversation

bpradipt
Copy link
Contributor

@bpradipt bpradipt commented Sep 4, 2024

No description provided.

@@ -88,6 +88,14 @@ spec:
value: registry.redhat.io/openshift-sandboxed-containers/osc-podvm-builder-rhel9:1.7.0
- name: RELATED_IMAGE_PODVM_PAYLOAD
value: registry.redhat.io/openshift-sandboxed-containers/osc-podvm-payload-rhel9:1.7.0
- name: RELEASE_VERSION
value: 1.7.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be inferred out of the version tag of one of the related images but I guess having an explicit env results in simpler code in the operator.

The latest CAA code shipped with 1.7.0 introduces breaking change
and requires cluster to be at latest 4.15 z stream.
To avoid breaking users on older versions, this code will patch
the CSV to refer to 1.6.0 CAA images

Signed-off-by: Pradipta Banerjee <[email protected]>
This includes base CSV file changes, RBAC changes etc.
These changes need to be manually incorporated in downstream builds

Signed-off-by: Pradipta Banerjee <[email protected]>
Inclusion of https://github.com/operator-framework/api/ v0.22.0 for
patching the operator CSV updates the controller-runtime deps which
requires to adapt the code.

v0.22.0 is the min version supporting golang 1.21 that is used to
build the 1.7.0 operator code.

Signed-off-by: Pradipta Banerjee <[email protected]>
@bpradipt bpradipt added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants