-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
10
-
False
-
-
False
-
?
-
?
-
test-operator-container-1.0.0-14
-
?
-
?
-
-
As of now test-operator expects certain resources to be present in the OSP 18 environment (like clouds.yaml) but we have no guarantees that such a resources will exist. This ticket is about adding a logic into openstack-operator that creates a test-operator CM that contains:
- information about which images should be used for testing
- where are resources consumed by test-oeprator (e.g., kubeconfig, clouds.yaml)
DoD:
- openstack-operator creates CM that contains all information required by the test-operator (info about images, resources like clouds.yml)
PRs:
https://github.com/openstack-k8s-operators/openstack-operator/pull/823(test-operator change needs to be merged first)https://github.com/openstack-k8s-operators/ci-framework/pull/1979https://github.com/openstack-k8s-operators/test-operator/pull/104https://github.com/openstack-k8s-operators/test-operator/pull/105
- is related to
-
OSPRH-2429 Make test-operator part of the openstack-operator-index
- Closed
- relates to
-
OSPRH-7627 Change test-operator-index to openstack-operator-index in test-operator role
- Backlog
-
OSPRH-7871 Consume CM created by the test-operator
- Closed