-
Notifications
You must be signed in to change notification settings - Fork 27
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
POWERMON-199: Use correct kepler namespace in must-gather #352
Conversation
8a7417b
to
22fec3d
Compare
@@ -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}') |
There was a problem hiding this comment.
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}
?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 ...
There was a problem hiding this 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
On a related topic, perhaps |
Signed-off-by: Vimal Kumar <vimal78@gmail.com>
22fec3d
to
34c9aba
Compare
Use labels to get correct namespace name.