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

[Spike] Investigate k8s compatibility with registry operator integration test suite #1312

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

[Spike] Investigate k8s compatibility with registry operator integration test suite #1312

michael-valdron opened this issue Oct 26, 2023 · 2 comments
Labels
area/registry Devfile registry for stacks and infrastructure 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

Comments

@michael-valdron
Copy link
Member

Which area/kind this issue is related to?

/area registry

Issue Description

At this time, k8s capability has has just been implemented within integration testing for the registry operator #1239 and has not been implemented in our CI yet. The test suite is also producing timeouts within the test cases when using k8s environment such as minikube.

In order to ensure our test suite has complete compatibility with k8s environments, we need to investigate the test suite's source code to see if there are additional changes needed to run our integration tests using Kubernetes.

Acceptance Criteria

  • Investigate test case source to find needed changes
  • Investigate utility function source for the test suite to find needed changes
  • Investigate test suite parameters to find needed changes
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Oct 26, 2023
@michael-valdron michael-valdron mentioned this issue Oct 26, 2023
Closed
3 tasks
@michael-valdron michael-valdron added the severity/blocker Issues that prevent developers from working label Oct 26, 2023
@michael-valdron michael-valdron changed the title Investigate k8s compatibility with registry operator integration test suite [Spike] Investigate k8s compatibility with registry operator integration test suite Oct 27, 2023
@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 26, 2024
@Jdubrick Jdubrick removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Mar 4, 2024
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Mar 4, 2024
@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 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
Projects
Devfile Project
Status: Done ✅
Milestone
No milestone
Development

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