Skip to content

Add skipRange on GitOps Z-stream releases for disconnected upgrades#147

Open
tzprograms wants to merge 2 commits into
rh-gitops-midstream:mainfrom
tzprograms:fix-skiprange-disconnected-upgrades
Open

Add skipRange on GitOps Z-stream releases for disconnected upgrades#147
tzprograms wants to merge 2 commits into
rh-gitops-midstream:mainfrom
tzprograms:fix-skiprange-disconnected-upgrades

Conversation

@tzprograms

Copy link
Copy Markdown

Summary

Fixes disconnected z-stream upgrades for OpenShift GitOps when customers mirror only a subset of operator bundles (e.g. 1.18.0 and 1.18.4 via ImageSetConfig) without intermediate patch releases.

Adds skipRange on patch bundles in channels gitops-1.18, gitops-1.19, and gitops-1.20 so OLM can upgrade directly within a minor version (e.g. 1.18.0 → 1.18.4) while keeping existing replaces edges.

Problem

Without in-minor skipRange, OLM requires every intermediate bundle in the catalog/registry. Disconnected customers must mirror all z-stream releases, increasing registry disk usage.

Changes

  • config.yamlskipRange for 1.18.1–1.18.6, 1.19.1–1.19.4, 1.20.1–1.20.4
  • Regenerated catalog/v4.14v4.22/template.yaml via generate-catalog-template.py

Example

openshift-gitops-operator.v1.18.4:

  • replaces: openshift-gitops-operator.v1.18.3 (unchanged)
  • skipRange: '>=1.18.0 <1.18.4' (new)

Jira

GITOPS-9586

@svghadi

svghadi commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

/ok-to-test

@svghadi

svghadi commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

/retest

Comment thread config.yaml Outdated
- name: openshift-gitops-operator.v1.19.1
replaces: openshift-gitops-operator.v1.19.0
skipRange: '>=1.0.0 <1.19.0'
skipRange: '>=1.0.0 <1.19.1'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should this be

Suggested change
skipRange: '>=1.0.0 <1.19.1'
skipRange: '>=1.19.0 <1.19.1'

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Yes it should be ideally, It was the value present by default hence I didn't touch it . If you want I can make the changes.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

yes. lets update it

Comment thread config.yaml Outdated
- name: openshift-gitops-operator.v1.19.2
replaces: openshift-gitops-operator.v1.19.1
skipRange: '>=1.0.0 <1.19.0'
skipRange: '>=1.0.0 <1.19.2'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Same as previous comment

@tzprograms tzprograms Jun 10, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Same as previous reply.

@tzprograms

Copy link
Copy Markdown
Author

/retest

@svghadi

svghadi commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

/ok-to-test

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.

2 participants