-
Notifications
You must be signed in to change notification settings - Fork 183
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
Fix Helm template naming in yaml files #174
Conversation
01d23c0
to
66df36a
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.
Thanks for fixing this!
@@ -12,26 +12,18 @@ We truncate at 63 chars because some Kubernetes name fields are limited to this | |||
If dryRun=true, we use fixed value "fluentd". |
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.
we can remove this comment
{{- $name := default .Chart.Name .Values.nameOverride -}} | ||
{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" }} | ||
{{- end -}} | ||
{{- end -}} | ||
|
||
{{/* | ||
Create default fully qualified labels. | ||
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec). | ||
If dryRun=true, we use the Chart name "sumologic" and do not include labels specific to Helm. |
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.
same here
cabf768
to
a686219
Compare
Description
Fixes both Helm and YAML-based deployment by standardizing on
collection-sumologic
app labels (removing "fluentd" all together).Also removes spurious
release: collection
in prometheus overrides, which was causing problems with YAML-based prometheus operator deployment.Testing performed