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

Helm chart: Ingress not working with release name #743

Open
clemenschuaccso opened this issue Oct 18, 2023 · 0 comments
Open

Helm chart: Ingress not working with release name #743

clemenschuaccso opened this issue Oct 18, 2023 · 0 comments

Comments

@clemenschuaccso
Copy link

In the file: https://github.com/keel-hq/keel/blob/master/chart/keel/templates/ingress.yaml
With a release named sandbox this will result to the following objects:
Ingress: sandbox-keel
Service: keel
But the Ingress is pointing to the service sandbox-keel which obviously does not exist.

service/keel manifest:

apiVersion: v1
kind: Service
metadata:
  labels:
    app: keel
    argocd.argoproj.io/instance: sandbox-keel
    chart: keel-1.0.2
    heritage: Helm
    release: sandbox-keel
  name: keel
  namespace: platform
spec:
  ports:
    - name: keel
      port: 9300
      protocol: TCP
      targetPort: 9300
  selector:
    app: keel
  sessionAffinity: None
  type: ClusterIP

ingress/sandbox-keel manifest:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
    app.kubernetes.io/instance: sandbox-keel
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: keel
    argocd.argoproj.io/instance: sandbox-keel
    helm.sh/chart: keel-1.0.2
  name: sandbox-keel
  namespace: platform
spec:
  rules:
    - host: SOME_HOSTNAME
      http:
        paths:
          - backend:
              service:
                name: sandbox-keel
                port:
                  name: keel
            path: /
            pathType: Prefix
 

Current workaround: set the value nameOverrideto sandbox-keel.
Possible fix: In Service manifest use fullname for name.

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

No branches or pull requests

1 participant