This repository has been archived by the owner on Jan 31, 2024. It is now read-only.
Add data-science-pipelines-operator label for DSPO manifests #784
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.
Description
If we do an
oc get pods -l app.kubernetes.io/created-by=data-science-pipelines-operator
after deploying DSP Operator, it won't return any pods, because only the DSPO deployment contains this label, the pods don't. Adding this label to the pods as well, so they could be filtered using the component name, that is, Data Science Pipelines Operator.Also, renamed the component to respect name-prefix, to make the service and service monitor consistent with DSPO (refer opendatahub-io/data-science-pipelines-operator#76)
How Has This Been Tested?
oc get pods -l app.kubernetes.io/created-by=data-science-pipelines-operator
in the same namespace where the operator is deployed. Make sure it displays DSPO pods.Merge criteria: