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

OpenShift 4.16 support for Registry Operator #1693

Open
3 tasks
michael-valdron opened this issue Mar 13, 2025 · 1 comment
Open
3 tasks

OpenShift 4.16 support for Registry Operator #1693

michael-valdron opened this issue Mar 13, 2025 · 1 comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Mar 13, 2025

/kind epic
/kind user-story

Which area is this user story related to?

/area registry

User Story

As a developer I want OpenShift 4.16 to be supported, so that I can install the registry operator using official means into my OpenShift 4.16 cluster.

As more users are using OpenShift 4.16 the need to support this version is essiential to ensure devfile services are up to date with compatibility and security patching. Given this is still a manual process, we'll need to exercise a few steps to provide the support to this version.

Acceptance Criteria

@openshift-ci openshift-ci bot added kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement area/registry Devfile registry for stacks and infrastructure labels Mar 13, 2025
@michael-valdron michael-valdron moved this to Refinement in Devfile Project Mar 13, 2025
@ibuziuk
Copy link

ibuziuk commented Mar 17, 2025

@michael-valdron please, make it available on 4.17 and 4.18 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement
Projects
Status: Refinement
Development

No branches or pull requests

2 participants