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

Fix ingress' service backend templating #70

Merged
merged 1 commit into from
May 11, 2023

Conversation

kang-makes
Copy link
Member

Ingress service is not using the withSuffix stanza, hence templating incorrectly compared with the service name.

Ingress was correctly deployed and its status is healthy because the ingress controller set the status, but there are not endpoints:

Labels:           app.kubernetes.io/instance=kang
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=stateless-dns
                  argocd.argoproj.io/instance=kang-dns
                  helm.sh/chart=stateless-dns-0.2.3
Namespace:        k-dns
Address:          46.4.181.74
Ingress Class:    kang
Default backend:  <default>
TLS:
  pdns-certs terminates pdns-api.kangmak.es
Rules:
  Host                 Path  Backends
  ----                 ----  --------
  pdns-api.kangmak.es
                       /   kang-stateless-dns:80 (<error: endpoints "kang-stateless-dns" not found>)
Annotations:           cert-manager.io/cluster-issuer: letsencrypt-prod-kang
                       nginx.ingress.kubernetes.io/auth-tls-secret: cert-manager/kang-ca
                       nginx.ingress.kubernetes.io/auth-tls-verify-client: on
Events:                <none>

@kang-makes kang-makes force-pushed the fix/ingress-incorrect-backend branch from 76bef75 to 6ce406f Compare May 11, 2023 19:39
Copy link
Member

@nadiamoe nadiamoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kang-makes kang-makes merged commit 9edfb46 into main May 11, 2023
@kang-makes kang-makes deleted the fix/ingress-incorrect-backend branch May 11, 2023 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants