[test-operator] Move to openstack-test-operator namespace #2600
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ce7fc9baf6b340efbd8148c19c1513f1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 46m 16s |
Test-operator is currently designed to be a cluster scoped
operator. This means it can watch and modify resources across all
OCP cluster.
This patch changes the operator to namespace scoped operator. By
default it is going to watch only:
- openstack-test-operator namespace: This is a namespace where
we recommend to install the test-operator. Prior to the
installation we recommend to create an OperatorGroup with
targetNamespaces value set to openstack-test-operator and
openstack.
- openstack: This is a namespace where the openstack controll
plane is deployed. Test-operator requires an access to this
namespace in order to read openstack specific CMs and Secrets
(e.g., clouds.yaml).
Depends-On: openstack-k8s-operators/ci-framework#2600
lpiwowar
force-pushed
the
namespace-scope
branch
from
8df929a to
ad1eca3
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/4743774be90a46c889af1d4fb5e8d7bf ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 11m 23s |
The test-operator got changed from cluster scoped operator to namespace scoped operator in this PR [1]. It is now recommended that the test-operator gets installed in a separate namespace other than the one where the test pods are spawned. This patch ensures that: - the test-operator gets installed in the openstack-test-operator namespace - the test-operator spawns test pods in the openstack namespace [1] openstack-k8s-operators/test-operator#264
lpiwowar
force-pushed
the
namespace-scope
branch
from
ad1eca3 to
042133f
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/9918fc55b5b24645ad8256fccdb4577a ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 05m 00s |
Test-operator is currently designed to be a cluster scoped
operator. This means it can watch and modify resources across all
OCP cluster.
This patch changes the operator to namespace scoped operator. By
default it is going to watch only:
- openstack-test-operator namespace: This is a namespace where
we recommend to install the test-operator. Prior to the
installation we recommend to create an OperatorGroup with
targetNamespaces value set to openstack-test-operator and
openstack.
- openstack: This is a namespace where the openstack controll
plane is deployed. Test-operator requires an access to this
namespace in order to read openstack specific CMs and Secrets
(e.g., clouds.yaml).
Depends-On: openstack-k8s-operators/ci-framework#2600
The test-operator got changed from cluster scoped operator to namespace scoped operator in this PR [1]. It is now recommended that the test-operator gets installed in a separate namespace other than the one where the test pods are spawned.
This patch ensures that:
the test-operator gets installed in the openstack-test-operator namespace
the test-operator spawns test pods in the openstack namespace
[1] openstack-k8s-operators/test-operator#264