Skip to content
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

Wrong name when installing as an helm dependency #97

Open
AnakinPt opened this issue Apr 4, 2023 · 0 comments
Open

Wrong name when installing as an helm dependency #97

AnakinPt opened this issue Apr 4, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@AnakinPt
Copy link

AnakinPt commented Apr 4, 2023

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.

@hurtadosanti hurtadosanti added the bug Something isn't working label May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants