Hello!
I am trying to setup nginx ingress on a bare metal environment. According to
https://github.com/kubernetes/ingress-nginx/blob/master/deploy/README.md#baremetal
the ingress service is exposed by "nodePort" like:
apiVersion: v1
kind: Service
metadata:
name: ingress-nginx
namespace: ingress-nginx
spec:
type: NodePort
ports:
- name: http
port: 80
targetPort: 80
protocol: TCP
- name: https
port: 443
targetPort: 443
protocol: TCP
selector:
app: ingress-nginx
For example, I created ingress resource to access a service by
"http://websvc.lab.local"; from outside. Then how to config the external DNS
entry? I am considering following options:
- Since all worker nodes in the cluster are listening to the node port,
just create a CNAME "websvc.lab.local" pointing to any 1 node IP? or
- find the node that currently hosts the ingress controller pod, and use
that IP? or
- create round robin DNS entries including all worker IPs?
But none of them seems reasonable. I searched for some time but did not
found a production-ready solution. Is there any recommendation about the
external part of ingress on bare metal?
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
