Kubernetes 带入口的反向代理

Question

I have to create an ingress as a reverse proxy to change the port used to call my external service. I have to use an Ingress because the LoadBalancer doesn't work on my local K8 cluster.

External Service

apiVersion: v1
kind: Service
metadata:
  name: extService
spec:
  type: ExternalName
  externalName: ext.serv.com

In my code, I have a hard-coded configuration that always uses port 8280 for extService calls. However, from my local cluster, I have to call extService with port 443

I develop the following Ingress

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: optcore-ingress
  annotations:
    kubernetes.io/ingress.class: nginx-ingress
spec:
  rules:
    - host: extSrvice
      http:
        paths:
          - path: /
            backend:
              serviceName: optcore
              servicePort: 443

But it doesn't work.

Answer 1

Well, ExternalName is meant to be used for workloads in your cluster to talk to something 'outside' your cluster.

Essentially, you are hijacking the use of an ExternalName service together with a Kubernetes Ingress resource/nginx ingress controller. So it's likely that it won't work. Also, an Ingress resource is supposed to work with a service inside your cluster (not outside).

If you really want your external service running on 8280 to listen on 443 . You can set up a regular reverse proxy with nginx, haproxy, etc in front of your service.

If for some reason you are running your 8280 service inside your cluster (you didn't specify this in your question) you can simply create an 'internal' (regular) service with port 443 and a targetPort of 8280 .