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

Problem with TLS ingress #2964

Open
Youpiiiii opened this issue Oct 3, 2024 · 2 comments
Open

Problem with TLS ingress #2964

Youpiiiii opened this issue Oct 3, 2024 · 2 comments
Labels
argo-cd cannot-reproduce Unable to reproduce issue. invalid Not a valid bug no-issue-activity

Comments

@Youpiiiii
Copy link

Youpiiiii commented Oct 3, 2024

Describe the bug

Bad generation of ingress

Related helm chart

argo-cd

Helm chart version

7.6.8

To Reproduce

helm install argocd argo/argo-cd -f argo-cd/values.yaml --dry-run
With this values:

server:
  ingress:
    enabled: true
    tls: true

Generate this ingress:

# Source: argo-cd/templates/argocd-server/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: argocd-server
  namespace: "argocd"
  labels:
    helm.sh/chart: argo-cd-5.36.7
    app.kubernetes.io/name: argocd-server
    app.kubernetes.io/instance: argocd
    app.kubernetes.io/component: server
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: argocd
    app.kubernetes.io/version: v2.7.6
spec:
  rules:
    - http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: argocd-server
                port:
                  number: 80
  tls:
    true

Why tls: true ?

Expected behavior

# Source: argo-cd/templates/argocd-server/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: argocd-server
  namespace: "argocd"
  labels:
    helm.sh/chart: argo-cd-5.36.7
    app.kubernetes.io/name: argocd-server
    app.kubernetes.io/instance: argocd
    app.kubernetes.io/component: server
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: argocd
    app.kubernetes.io/version: v2.7.6
spec:
  rules:
    - http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: argocd-server
                port:
                  number: 80
  tls:
    - secretName: argocd-server-tls
      hosts:
      - argocd.example.com

Screenshots

No response

Additional context

No response

@Youpiiiii Youpiiiii added the bug Something isn't working label Oct 3, 2024
@mkilchhofer
Copy link
Member

mkilchhofer commented Oct 16, 2024

Are you sure? Your reprod steps are inconsistent. You are talking about helm chart version 7.6.8 and your rendered YAML says:

# ..
  labels:
    helm.sh/chart: argo-cd-5.36.7 # <- this means chart version 5.36.7
# ..

You need to update the Helm chart version to the latest (2 new Major versions) to use tls: true. The Helm chart version 5.36.x is using another structure:

{{- with .Values.server.ingress.tls }}
tls:
{{- toYaml . | nindent 4 }}
{{- end -}}


Update: Ah maybe you are using an old repo cache as your command does not specify a version excplicitly

- helm install argocd argo/argo-cd -f argo-cd/values.yaml --dry-run
+ helm install argocd argo/argo-cd -f argo-cd/values.yaml --version 7.6.8 --dry-run

@mkilchhofer mkilchhofer added invalid Not a valid bug cannot-reproduce Unable to reproduce issue. and removed bug Something isn't working labels Oct 16, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd cannot-reproduce Unable to reproduce issue. invalid Not a valid bug no-issue-activity
Projects
None yet
Development

No branches or pull requests

2 participants