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 registry operator to use OpenShift 4.18 testing #1669

Open
3 tasks
Tracked by #1693
michael-valdron opened this issue Jan 9, 2025 · 1 comment
Open
3 tasks
Tracked by #1693

Upgrade registry operator to use OpenShift 4.18 testing #1669

michael-valdron opened this issue Jan 9, 2025 · 1 comment
Labels
area/ci area/registry Devfile registry for stacks and infrastructure

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Jan 9, 2025

Which area is this issue related to?

/area ci
/area registry

Issue Description

With the need to support OpenShift 4.16+, it makes sense to update testing to target the newest OCP version in this range which is 4.18.

Acceptance Criteria

  • Test registry operator on OpenShift 4.16-4.18 to ensure compatibility
  • Document and add to the acceptance criteria any additional tasks needed to ensure compatibility
  • Update the testing configs and jobs to use OCP 4.18
@openshift-ci openshift-ci bot added area/ci area/registry Devfile registry for stacks and infrastructure labels Jan 9, 2025
@michael-valdron michael-valdron moved this to Refinement in Devfile Project Jan 9, 2025
@yangcao77 yangcao77 moved this from Refinement to Backlog in Devfile Project Feb 19, 2025
@michael-valdron
Copy link
Member Author

Setting new target for updated OCP versions under #1693.

@michael-valdron michael-valdron changed the title Upgrade registry operator to use OpenShift 4.16 testing Upgrade registry operator to use OpenShift 4.18 testing Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/registry Devfile registry for stacks and infrastructure
Projects
Status: Backlog
Development

No branches or pull requests

1 participant