Skip to content

Allow OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION override#80

Merged
openshift-merge-bot[bot] merged 1 commit into
openstack-lightspeed:mainfrom
lpiwowar:lpiwowar/openshift-lightspeed-version
Feb 11, 2026
Merged

Allow OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION override#80
openshift-merge-bot[bot] merged 1 commit into
openstack-lightspeed:mainfrom
lpiwowar:lpiwowar/openshift-lightspeed-version

Conversation

@lpiwowar

@lpiwowar lpiwowar commented Feb 5, 2026

Copy link
Copy Markdown
Contributor

Add support for setting OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION variable during 'make bundle' to override the default 'latest' value.

@openshift-ci

openshift-ci Bot commented Feb 5, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci

openshift-ci Bot commented Feb 5, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lpiwowar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Feb 5, 2026
Add support for setting OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION variable
during 'make bundle' to override the default 'latest' value.
@lpiwowar lpiwowar force-pushed the lpiwowar/openshift-lightspeed-version branch from 07ab62f to 9460455 Compare February 5, 2026 13:49
@lpiwowar

lpiwowar commented Feb 5, 2026

Copy link
Copy Markdown
Contributor Author

/test all

@lpiwowar lpiwowar marked this pull request as ready for review February 5, 2026 15:40
@umago

umago commented Feb 11, 2026

Copy link
Copy Markdown
Contributor

Thanks for the patch! It /lgtm

@umago

umago commented Feb 11, 2026

Copy link
Copy Markdown
Contributor

/lgtm

Comment thread Makefile
cd config/manager && $(KUSTOMIZE) edit add patch --kind Deployment --name controller-manager --patch "[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/env/0/value\", \"value\": \"$(OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION)\"}]"
$(KUSTOMIZE) build config/manifests | $(OPERATOR_SDK) generate bundle $(BUNDLE_GEN_FLAGS)
$(OPERATOR_SDK) bundle validate ./bundle
cd config/manager && $(KUSTOMIZE) edit remove patch --kind Deployment --name controller-manager --patch "[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/env/0/value\", \"value\": \"$(OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION)\"}]"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think we should remove this line, that way the files we leave are the ones that have been validated.
That's the pattern used in the other operators https://github.com/openstack-k8s-operators/openstack-operator/blob/3c0eba8e939b80f2cb9331e874080a0c8208d73e/Makefile#L402

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thanks! -> #81

@openshift-merge-bot openshift-merge-bot Bot merged commit 2e170ee into openstack-lightspeed:main Feb 11, 2026
7 checks passed
lpiwowar added a commit to lpiwowar/operator that referenced this pull request Feb 11, 2026
Retain patch modifications in config/manager/kustomization.yaml
instead of removing them after bundle generation. This aligns with
the pattern used in the openstack-k8s-operators namespace.

The Makefile no longer removes the deployment patch, keeping the
kustomization file consistent with the generated bundle.

Implements request in this comment [1].

[1] openstack-lightspeed#80 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants