Helm chart: Ingress not working with release name

[clemenschuaccso]

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.

[icsy7867]

Sorry for the stupid question, but where exactly would you add "nameOverride"? Would this be in the ingress? Or the values.yaml or somewhere for the actual keel deployment?

I am running into what I think is the same issue. If I shell into the container running in kubernetes and I do a:
curl localhost:9300 I get HTML back. But if I setup an ingress to that server (Cluster service on port 9300) I just get a 503 back.