-
Notifications
You must be signed in to change notification settings - Fork 399
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
feat(helm): All recommended Kubernetes labels #1538
Conversation
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.
Think it's a good idea to move Values.additionalLabels to _helpers.tpl.
But there is no need to separately define app.kubernetes.io/component
for each object, see my comment below.
I'm also happy that you don't update the selectorLabels
, since it was a pain to update last time.
There is no need to bump the helm chart, we do that in CI.
app.kubernetes.io/part-of: grafana-operator | ||
{{- with .Values.additionalLabels }} | ||
{{ toYaml . }} | ||
{{- end }} |
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.
This I think is a good idea
{{- toYaml . | nindent 4 }} | ||
{{- end }} | ||
{{- include "grafana-operator.labels" . | nindent 4 }} | ||
app.kubernetes.io/component: config |
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 don't agree with your interpretation of how app.kubernetes.io/component
should be used.
The component is related to the whole object, in this case grafana-operator
. It doesn't differ between object like rbac or network.
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.
@NissesSenap so what do you like for this label ? just grafana-operator
or operator
?
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.
operator
I guess
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.
done.
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
feat(helm): All recommended Kubernetes labels
@@ -21,9 +19,7 @@ spec: | |||
{{- end }} | |||
labels: | |||
{{- include "grafana-operator.selectorLabels" . | nindent 8 }} |
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.
grafana-operator.selectorLabels
don't include .Values.additionalLabels
, so removing the with
block is a breaking change; since this change landed, it's not possible to set additional pod labels.
I believe this can be easily fixed by including grafana-operator.labels
instead:
{{- include "grafana-operator.selectorLabels" . | nindent 8 }} | |
{{- include "grafana-operator.labels" . | nindent 8 }} |
Add missing labels and refactoring additional labels.
I don't change Helm chart version, because it is
v0.1.4
but in documentation, it isv5.9.0
: