We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bitnami/apache
None
Hello,
I am having error when I try to deploy helm chart apache 11.3.1 version, and when I try to turn on metrics field:
EKS 1.31 version
--set="metrics.enabled=true"
Install metrics with apache exporter sidecar container
template: apache/templates/networkpolicy.yaml:44:26: executing "apache/templates/networkpolicy.yaml" at <.Values.metrics.containerPorts.metrics>: nil pointer evaluating interface {}.metrics
similar to this issue but different chart #23172
The text was updated successfully, but these errors were encountered:
Hi!
Thank you so much for reporting. Indeed, in networkpolicy.yaml file there is an error. Instead of
- port: {{ .Values.metrics.containerPorts.metrics }}
It should be
- port: {{ .Values.metrics.containerPort }}
As you discovered the issue, would you like to submit a PR applying this change?
Sorry, something went wrong.
javsalgar
No branches or pull requests
Name and Version
bitnami/apache
What architecture are you using?
None
What steps will reproduce the bug?
Hello,
I am having error when I try to deploy helm chart apache 11.3.1 version, and when I try to turn on metrics field:
EKS 1.31 version
Are you using any custom parameters or values?
--set="metrics.enabled=true"
What is the expected behavior?
Install metrics with apache exporter sidecar container
What do you see instead?
template: apache/templates/networkpolicy.yaml:44:26: executing "apache/templates/networkpolicy.yaml" at <.Values.metrics.containerPorts.metrics>: nil pointer evaluating interface {}.metrics
Additional information
similar to this issue but different chart #23172
The text was updated successfully, but these errors were encountered: