You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: