Change scope of test-operator to namespace #264
Draft
+134
−62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lpiwowar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
lpiwowar
force-pushed
the
namespace-scoped-operator
branch
2 times, most recently
from
7fd0f3a to
ad48997
Compare
lpiwowar
added a commit
to openstack-k8s-operators/ci-framework
that referenced
this pull request
Dec 12, 2024
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-scoped-operator
branch
from
ad48997 to
2f211b0
Compare
lpiwowar
added a commit
to openstack-k8s-operators/ci-framework
that referenced
this pull request
Dec 12, 2024
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
added a commit
to openstack-k8s-operators/ci-framework
that referenced
this pull request
Dec 17, 2024
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-scoped-operator
branch
from
2f211b0 to
883001d
Compare
lpiwowar
added a commit
to openstack-k8s-operators/ci-framework
that referenced
this pull request
Dec 19, 2024
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
|
/test all |
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-scoped-operator
branch
from
883001d to
81c09bd
Compare
|
/test all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).