Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Change namespace to openstack-test-operator #265

Closed
wants to merge 1 commit into from

Conversation

lpiwowar
Copy link
Collaborator

Recently we changed the test-operator from cluster scoped to namespace
scoped operator. This patch ensures that we reflect this change in the
test-operator documentation.

Recently we changed the test-operator from cluster scoped to namespace
scoped operator. This patch ensures that we reflect this change in the
test-operator documentation.
Copy link

openshift-ci bot commented Dec 12, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

openshift-ci bot commented Dec 12, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lpiwowar
Copy link
Collaborator Author

/test all

@@ -152,14 +189,14 @@ Please make sure that you follow the order of the steps:

.. code-block:: bash

oc delete operator/test-operator.openstack-operators
oc delete operator/test-operator.openstack-test-operator

7. Check that there are no test-operator related resources hanging. This step
is not required.

.. code-block:: bash

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The deletion of OperatorGroup is missing, so after following the steps it's not a completely clean environment.

oc delete operatorgroup.operators.coreos.com/test-operator -n openstack-test-operator This worked for deletion, but maybe there is better way to do it 😄


.. code-block:: bash

oc new-project openstack-test-operator
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The project is created, but never deleted. I am not sure if that is intentional. If yes, please ignore this comment.

@@ -76,6 +101,18 @@ project.
test-operator-controller-manager-6c9994847c-6jwn5 2/2 Running 0 20s
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line need to be changed into oc get pods -n openstack-test-operator, that is where te controller manager is newly created.

@@ -50,24 +76,23 @@ project.
kind: Subscription
metadata:
name: test-operator
namespace: openstack-operators
namespace: openstack-test-operator
spec:
name: test-operator
source: openstack-operator-index
sourceNamespace: openstack-operators
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that the sourceNamespace: openstack-operators should also be changed into opentack-test-operator. Or at least that is how my testing yaml for this patch worked correctly.


5. Remove test-operator related installplan (replace :code:`XXXXX` with value obtained
with the first command :code:`oc get installplans`)

.. code-block:: bash

oc get installplans -n openstack-operators | grep "test-operator"
oc get installplans -n openstack-test-operator | grep "test-operator"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I test the patch, I didn't find any installplans in openstack-test-operator namespace. Don't know why that is, maybe it was fault in my testing, but I still wanted to ask about this.

@lpiwowar
Copy link
Collaborator Author

Thank you @kstrenkova for the review!:) I'm closing the PR because we agreed not to switch the test-operator to a namespace scoped operator. The discussion can be found here -> #264

@lpiwowar lpiwowar closed this Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants