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.

Sign up for GitHub

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

Jump to bottom

Implement k8s compatibility changes for registry operator integration test suite #1313

Closed
3 tasks
michael-valdron opened this issue Oct 26, 2023 · 2 comments
Closed
3 tasks

Implement k8s compatibility changes for registry operator integration test suite #1313

michael-valdron opened this issue Oct 26, 2023 · 2 comments
Labels
area/registry Devfile registry for stacks and infrastructure kind/user-story User story for new enhancement lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. severity/blocker Issues that prevent developers from working status/blocked

Comments

@michael-valdron
Copy link
Member

/kind user-story

Which area this user story is related to?

/area registry

User Story

As a registry operator developer I want to be to run testing of my source under Kubernetes, so that I can more effectively and efficiently ensure k8s capability with the registry operator.

After investigating changes needed to the integration test suite #1312, we want to implement those changes so that the integration test suite can run under Kubernetes environments as well as ensuring the test suite continues to run under OpenShift environments.

Acceptance Criteria
@openshift-ci openshift-ci bot added kind/user-story User story for new enhancement area/registry Devfile registry for stacks and infrastructure labels Oct 26, 2023
@michael-valdron michael-valdron mentioned this issue Oct 26, 2023
Closed
1 task
@michael-valdron michael-valdron added status/blocked severity/blocker Issues that prevent developers from working labels Oct 26, 2023
@michael-valdron michael-valdron mentioned this issue Oct 27, 2023
Merged
3 tasks
@michael-valdron michael-valdron mentioned this issue Nov 20, 2023
Merged
3 tasks
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Jan 25, 2024
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Mar 4, 2024
@Jdubrick Jdubrick removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Mar 4, 2024
@michael-valdron michael-valdron mentioned this issue Aug 13, 2024
Merged
3 tasks
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 22, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Nov 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2024
@github-project-automation github-project-automation bot moved this from Refinement to Done ✅ in Devfile Project Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/registry Devfile registry for stacks and infrastructure kind/user-story User story for new enhancement lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. severity/blocker Issues that prevent developers from working status/blocked
Projects
Devfile Project
Status: Done ✅
Milestone
No milestone
Development

No branches or pull requests
2 participants
@michael-valdron @Jdubrick