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

remove hard-coded namespace from noobaa #218

Merged
merged 1 commit into from
Feb 4, 2025
Merged

Conversation

yati1998
Copy link
Member

this commit removes the hard-coded namespace
for noobaa collection to collect all the
resources in correct namespace

this commit removes the hard-coded namespace
for noobaa collection to collect all the
resources in correct namespace

Signed-off-by: yati1998 <[email protected]>
@black-dragon74
Copy link
Member

Hi @yati1998

I guess lines 68 and 77 needs updating as well (maybe moved into for block)?

for pod in $(oc -n "${ns}" get pods -l "${NOOBAA_POSTGRES_LABEL}" | grep -v NAME | awk '{print $1}'); do

NOOBAA_RECONCILE_STRATEGY=$(oc -n "${ns}" get storagecluster -o jsonpath='{.items[0].spec.multiCloudGateway.reconcileStrategy}' 2>/dev/null)

What is the value of ns supposed to be here? Was it wrongly interpreted all this time?

P.S: The INSTALL_NAMESPACE changes LGTM. Just pointing out what I stumbled across while reviewing.

Regards

@agarwal-mudit
Copy link
Member

/cherry-pick release-4.18

@openshift-cherrypick-robot

@agarwal-mudit: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@agarwal-mudit
Copy link
Member

@black-dragon74 @yati1998 Can this PR be merged?

@agarwal-mudit
Copy link
Member

/cherry-pick release-4.17

@openshift-cherrypick-robot

@agarwal-mudit: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@black-dragon74
Copy link
Member

@black-dragon74 @yati1998 Can this PR be merged?

Sure, I have opened a new issue to track the changes that I requested on this PR :)

@black-dragon74
Copy link
Member

/lgtm
/approve

Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: black-dragon74, yati1998

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:
  • OWNERS [black-dragon74,yati1998]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 69e99aa into main Feb 4, 2025
7 checks passed
@openshift-cherrypick-robot

@agarwal-mudit: new pull request created: #225

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@agarwal-mudit: new pull request created: #226

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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.

4 participants