This repository has been archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Support fullnameOverride (Kibana chart) #267
Labels
enhancement
New feature or request
Comments
This is inconsistent with elasticsearch's helm chart (which does not use the Release name at all--the service is always just named "elasticsearch-master"). |
I agree. My pod names are:
Please fix-fix |
tusciucalecs
pushed a commit
to tusciucalecs/helm-charts
that referenced
this issue
Oct 15, 2019
tusciucalecs
pushed a commit
to tusciucalecs/helm-charts
that referenced
this issue
Oct 15, 2019
tusciucalecs
pushed a commit
to tusciucalecs/helm-charts
that referenced
this issue
Oct 15, 2019
tusciucalecs
added a commit
to tusciucalecs/helm-charts
that referenced
this issue
Oct 15, 2019
tusciucalecs
added a commit
to tusciucalecs/helm-charts
that referenced
this issue
Oct 15, 2019
4 tasks
jmlrt
added a commit
that referenced
this issue
Nov 18, 2019
[Issue #267] Support fullnameOverride in kibana, filebeat, metricbeat…
I'm closing this issue as it was implemented in #330 |
Thanks @tusciucalecs, you are a hero-hero! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the feature:
Currently "fullname" helper macro provides name to service, ingress etc. and it uses release name, chart name (and optionally you can input "nameOverride") and this results in a "x-y" construct.
Allowing the user to specify
fullnameOverride
in values file will give additional flexibility with naming resources.Examples:
https://github.com/helm/charts/blob/master/stable/grafana/templates/_helpers.tpl
https://github.com/helm/charts/blob/master/stable/prometheus/templates/_helpers.tpl
Describe a specific use case for the feature:
I want my service, ingress and other resources to be named just "kibana", without any prefix, like "monitoring-kibana" (because they are anyway in the "monitoring" namespace in my case so it's redundant).
The text was updated successfully, but these errors were encountered: