-
Notifications
You must be signed in to change notification settings - Fork 3.9k
feat(helm): Make helm labels more specific for antiaffinity #17405
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
updates values to use the new labels Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
Signed-off-by: Jirapong Pansak <55589246+MaoMaoCake@users.noreply.github.com>
jkroepke
left a comment
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.
Please check my comments.
| app.kubernetes.io/instance: loki | ||
| app.kubernetes.io/name: loki |
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.
| app.kubernetes.io/instance: loki | |
| app.kubernetes.io/name: loki | |
| app.kubernetes.io/name: '{{ include "loki.name" . }}' | |
| app.kubernetes.io/instance: '{{ .Release.Name }}' |
this would match
loki/production/helm/loki/templates/_helpers.tpl
Lines 139 to 145 in a091428
| {{/* | |
| Selector labels | |
| */}} | |
| {{- define "loki.selectorLabels" -}} | |
| app.kubernetes.io/name: {{ include "loki.name" . }} | |
| app.kubernetes.io/instance: {{ .Release.Name }} | |
| {{- end }} |
But affinity need to be pass trough the helm tpl function everywhere, which is fine to solve this case in idiomatic way.
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.
Ill make this change would you prefer I made a new pull request without the _helpers-xxx changes?
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.
Can you modify this existing here, if you wish. both is fine.
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 commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
…grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
grafana#17404) This commit allows templating in the affinity and topology spread constraints, and updates the values to be more specific about the app.kubernetes.io/instance and app.kubernetes.io/name kubernetes recommended label. When deploying into a cluster with a low number of nodes, or a cluster with the app.kubernetes.io/component label already used extensively, you cannot place these pods. If we want them to be scheduled apart, we should be more specific with the label selector. This follows on from the draft PR grafana#17405
What this PR does / why we need it:
Makes the labels for loki pods more specific so as to not cause issues when using with mimir.
Which issue(s) this PR fixes:
Fixes #17404
Special notes for your reviewer:
Checklist
CONTRIBUTING.mdguide (required)featPRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.mddeprecated-config.yamlanddeleted-config.yamlfiles respectively in thetools/deprecated-config-checkerdirectory. Example PR