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
I use the Helm chart as a dependency of another service I use, so I can ramp up everything at once.
In my chart.yaml file I added this:
dependencies: - name: hivemq-operator version: 0.11.17 repository: https://hivemq.github.io/helm-charts condition: hivemq-operator.enabled
then in the values.yamlI added this:
hivemq-operator: enabled: true namespaceOverride: hivemq nameOverride: hivemq fullnameOverride: hivemq global: rbac: pspEnabled: false
When I run the command:
helm upgrade -i foo .
I expect to have in the hivemq namespace a deployment named hivemq for the cluster, but I found 3 pods named "foo".
I presume this happens because in the cluster-deployment.yaml file it's using "{{ spec.name }}" and not allowing a name override from the user.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I use the Helm chart as a dependency of another service I use, so I can ramp up everything at once.
In my chart.yaml file I added this:
then in the values.yamlI added this:
When I run the command:
I expect to have in the hivemq namespace a deployment named hivemq for the cluster, but I found 3 pods named "foo".
I presume this happens because in the cluster-deployment.yaml file it's using "{{ spec.name }}" and not allowing a name override from the user.
The text was updated successfully, but these errors were encountered: