[Bug]: When there is service type ExternalName upstream is not getting populated

[medicharlachiranjeevi]

Version

edge

What Kubernetes platforms are you running on?

Other

Steps to reproduce

1. We had deployed nginx ingress with the plus version, and our chart version is 5.1.0.
2. We are trying to connect other namespace SVC using the Type ExternalName service. We tried curl, telnet, and ping everything is working fine.

Service:

apiVersion: v1
kind: Service
metadata:
  labels:
  name: external-ingress-*****
spec:
  externalName: servicename.**-**-lab.svc.cluster.local
  ports:
  - name: https
    port: 443
    protocol: TCP
    targetPort: 443
  sessionAffinity: None
  type: ExternalName
status:
  loadBalancer: {}

Ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
  name: namespace
spec:
  rules:
  - host: ****-***.dummy.com
      - backend:
          service:
            name: external-ingress-*****
            port:
              number: 443
        path: /path
        pathType: Prefix

Inside the nginx config, at the upstream service config is empty, and it's giving no active upstream.

nginx upstream config:

upstream ****-443 {
    zone *****-443 512k;
    least_conn;
}

[github-actions]

Hi @medicharlachiranjeevi thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[pdabelf5]

@medicharlachiranjeevi your ingress spec seems to be missing the http & paths blocks. For example

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  ingressClassName: nginx
  rules:
  - host: example.com
    http:
      paths:
      - backend:
          service:
            name: my-service
            port:
              number: 80
        path: /path
        pathType: Prefix

[danielnginx]

@medicharlachiranjeevi does it solve your issue?

[medicharlachiranjeevi]

Hi, we went with mergeable ingress.