You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#28543 has been implemented with an incorrect reference to the basePath parameter is now required to be appended exactly after the publicBasePath parameter
but the automatic placement template in templates/configmap.yaml it is referenced incorrectly as below
data:
kibana.yml: | pid.file: /opt/bitnami/kibana/tmp/kibana.pid server.host: {{ .Values.configuration.server.host | quote }} server.port: {{ .Values.containerPorts.http }} elasticsearch.hosts: [{{ include "kibana.elasticsearch.url" . }}] {{- if .Values.configuration.server.basePath }} server.basePath: {{ .Values.configuration.server.basePath | quote }} {{- end }} {{- if or .Values.configuration.server.publicBaseUrl .Values.ingress.enabled }} server.publicBaseUrl: {{ default .Values.ingress.hostname .Values.configuration.server.publicBaseUrl }} {{- end }} server.rewriteBasePath: {{ .Values.configuration.server.rewriteBasePath }}
Details
When a custom configuration is used for kibana to be served behind ingress ( ingress-nginx in our case ), the newer version of kibana expects that the basePath should be automatically appended after the .Values.ingress.hostname or the value of .Values.configuration.server.publicBaseUrl which if NOT Set, will be set to only the .Values.ingress.hostname, resulting in error of bother basePath and publicBaseUrl are incorrect
Ideally it should
{{- if or .Values.ingress.tls .Values.ingress.extraTls }}{{- $scheme := "https://" }}{{- else }}{{- $scheme := "http://" }}{{- end }} {{- if and ( not .Values.configuration.server.publicBaseUrl) .Values.ingress.enabled }}server.publicBaseUrl: {{ $scheme }}{{ .Values.ingress.hostname }}/{{ .Values.configuration.server.basePath }}{{- else }}server.publicBaseUrl: {{ $scheme }}{{ .Values.configuration.server.publicBaseUrl }}/{{ .Values.configuration.server.basePath }}{{- end }}
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Name and Version
bitnami/kibana 11.4.0
What architecture are you using?
amd64
What steps will reproduce the bug?
#28543 has been implemented with an incorrect reference to the
basePath
parameter is now required to be appended exactly after thepublicBasePath
parameterbut the automatic placement template in
templates/configmap.yaml
it is referenced incorrectly as belowDetails
When a custom configuration is used for kibana to be served behind ingress ( ingress-nginx in our case ), the newer version of kibana expects that the
basePath
should be automatically appended after the.Values.ingress.hostname
or the value of.Values.configuration.server.publicBaseUrl
which if NOT Set, will be set to only the.Values.ingress.hostname
, resulting in error of botherbasePath
andpublicBaseUrl
are incorrectIdeally it should
Are you using any custom parameters or values?
#28543
What is the expected behavior?
#28543
What do you see instead?
#28543
Additional information
#28543
The text was updated successfully, but these errors were encountered: