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

Upgrade all OLM versions -- including v5.6.0 -- directly to latest #1476

Conversation

melledouwsma
Copy link
Contributor

As discussed in #1438 (comment), here's a Pull Request that fixes the OLM upgrade tree on OpenShift for v5.6.0. This commit resets the upgrade tree by forcing all releases since v5.6.0 to upgrade directly to the latest version.

When a new release is cut and admitted to OLM, this change will be included and will restore the upgrade tree.

@CLAassistant
Copy link

CLAassistant commented Mar 26, 2024

CLA assistant check
All committers have signed the CLA.

@@ -559,7 +559,11 @@ spec:
name: manager
- image: ghcr.io/grafana/grafana-operator@sha256:97561cef949b58f55ec67d133c02ac205e2ec3fb77388aeb868dacfcebad0752
name: grafana-operator-97561cef949b58f55ec67d133c02ac205e2ec3fb77388aeb868dacfcebad0752-annotation
replaces: grafana-operator.v5.6.2
replaces: grafana-operator.v5.6.0
Copy link
Collaborator

Choose a reason for hiding this comment

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

How will this affect the replacement of 5.8.0? Will the 5.8.0 users get 5.8.1 as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, all versions specified in the skips block will update to 5.8.1, including 5.8.0. It's based on this concept: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/how-to-update-operators.md#skipping-updates

@NissesSenap NissesSenap enabled auto-merge (squash) April 3, 2024 09:21
@NissesSenap NissesSenap merged commit 720e742 into grafana:master Apr 3, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants