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

POWERMON-199: Use correct kepler namespace in must-gather #352

Merged

Conversation

vimalk78
Copy link
Collaborator

Use labels to get correct namespace name.

@@ -17,7 +17,7 @@

set -eu -o pipefail

export KEPLER_NS="kepler-operator"
export KEPLER_NS=$(oc get ns -l app.kubernetes.io/managed-by=kepler-operator --output=jsonpath='{.items[*].metadata.name}')
Copy link
Collaborator

Choose a reason for hiding this comment

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

perhaps only the first item instead of all items in the list?
jsonpath={.items[0].metadata.name} ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ideally there should be only 1.

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes, indeed .. already approved.
In a different PR, I think it is better to iterate on all namespaces to capture the details. That way we get all namespaces (perhaps user has both community and power-mon installed) etc ...

Copy link
Collaborator

@sthaha sthaha left a comment

Choose a reason for hiding this comment

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

I think -o name may be

@sthaha
Copy link
Collaborator

sthaha commented Jan 28, 2024

On a related topic, perhaps status.deploymentNamespace can be added to kepler.

Signed-off-by: Vimal Kumar <vimal78@gmail.com>
@sthaha sthaha force-pushed the fix-must-gather-ns branch from 22fec3d to 34c9aba Compare January 29, 2024 01:18
@sthaha sthaha merged commit ad7857f into sustainable-computing-io:v1alpha1 Jan 29, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants