Skip to content

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

Closed as not planned
@michael-valdron

Description

@michael-valdron

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/registryDevfile registry for stacks and infrastructurelifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.severity/blockerIssues that prevent developers from working

    Type

    No type

    Projects

    Status

    Done ✅

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions