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

overrideNamespace is not propagated to redis-secret #2817

Closed
nikolaof opened this issue Jul 9, 2024 · 1 comment · Fixed by #2821
Closed

overrideNamespace is not propagated to redis-secret #2817

nikolaof opened this issue Jul 9, 2024 · 1 comment · Fixed by #2821
Assignees
Labels
argo-cd bug Something isn't working

Comments

@nikolaof
Copy link

nikolaof commented Jul 9, 2024

Describe the bug

When creating an umbrella (wrapper) helm chart to deploy argocd and use the overrideNamespace attribute in values the redis-secret is created to the default namespace and not in the defined one. This makes all pods except the applicationset one unable to start. They return an error redis-secret not found

Related helm chart

argo-cd

Helm chart version

7.3.4

To Reproduce

Create an umbrella chart like this

Chart.yaml

apiVersion: v2
name: argo-cd
version: 1.0.2
dependencies:
  - name: argo-cd
    version: 7.3.4
    repository: https://argoproj.github.io/argo-helm

values.yaml

argo-cd:
  namespaceOverride: argo-cd
  dex:
    enabled: false
  notifications:
    enabled: false
  applicationSet:
    enabled: false
  server:
    extraArgs:
      - --insecure

Expected behavior

To create the redis-secret in the defined namespace, so the pods can access it.

Screenshots

No response

Additional context

What I did was to change locally the following lines:

namespace: {{ .Release.Namespace | quote }}

namespace: {{ .Release.Namespace | quote }}

namespace: {{ .Release.Namespace | quote }}

namespace: {{ .Release.Namespace | quote }}

and replace them with the following:

namespace: {{ include  "argo-cd.namespace" . }}

Then I used this modified version of argo-cd chart to build my umbrella chart and everything was deployed correctly without errors.

Shall I create a PR to commit these changes or it is not the proper way to do it?

@mkilchhofer
Copy link
Member

mkilchhofer commented Jul 10, 2024

Hi @nikolaof

Thanks for reporting that 👍 .
I created a PR to address that issue:

@mkilchhofer mkilchhofer self-assigned this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants