-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Respect deployment labels in the CSV #5533
Respect deployment labels in the CSV #5533
Conversation
/assign @camilamacedo86 |
@camilamacedo86 the "sanity / docs" job seemed to have some connection issues. Is there a way to retrigger this? |
@fabianvf can you help me with this? |
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.
Apart from the one issue of adding webhookPath
in samples, rest seem fine.
webhookPath: /validate-cache-example-com-v1alpha1-memcached |
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.
Curious, why does the webhook
path get added? Webhookdefinitions
are defined in operator-framework/api
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.
It only added a newline at the end of the file. Same as with https://github.com/operator-framework/operator-sdk/pull/5533/files#diff-bd889e1aa1c1539a692594a301ce58562dd1f903280a9c0a324d8503a2f8b1eaR212.
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.
Sorry, my bad. Overlooked it.
Thanks @varshaprasad96 for having a review on it. I added comments to your findings. For sure I can change it as well... |
239702a
to
288c8bc
Compare
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.
Thank you for your contribution. 🥇
It shows fine for me
/approved
I think would be nice we get +1 reviewer before it gets merged. (to lgtm)
This change adds the labels of the deployment to the ClusterServiceVersions deployment spec. So the labels defined for the deployment (and defined in its manifest) will be applied too, if the operator gets installed via OLM. Signed-off-by: Christoph Stäbler <[email protected]>
288c8bc
to
bd079cd
Compare
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.
Looks good to me to! Thanks!
/lgtm
/retest-required |
@creydr: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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/test-infra repository. |
@camilamacedo86 @varshaprasad96 thanks for your review and lgtm. |
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.
/lgtm
Description of the change:
This change adds the labels of the deployment to the ClusterServiceVersions
DeploymentSpecs
. So the labels defined for the deployment (and defined in its manifest) will be applied too, if the operator gets bundled and installed via OLM.Motivation for the change:
Currently the CSV does not contain the labels of the deployment in the deployment spec, even there is a field for it (clusterserviceversion_types.go#L71).
This leads to missing labels of the deployment, when the operator is bundled and installed via OLM. This PR addresses it and adds the deployment labels to the CSV.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
) <- not sure if this fix is seen as user-facing change.website/content/en/docs