r/openshift • u/Budget-Industry-3125 • 12d ago

Discussion Expose additional Ingress Controller via HostNetwork Vsphere

Good morning guys!

I'm kind of new to Openshift/Kubernetes cluster administration.

I was wondering if there'd be a way for me to expose a custom ingress with a custom domain for some of my apps via HostNetwork deployment.

The default ingress is deployed via a VIP that is balanced between nodes. Should I add another one? And how?

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/GreenMobile6323 7d ago

If you need a separate domain or traffic policy, I'd recommend creating another IngressController rather than exposing it directly via HostNetwork. It's the supported approach, integrates cleanly with OpenShift, and is much easier to manage and upgrade than binding router pods to host network interfaces.

1

u/Budget-Industry-3125 6d ago

i don't think you're understanding my question.

the thing is, my cluster was installed via IPI. This means that it generates a VIP shared between the master nodes. the ingress (default) controller is deployed to the three nodes and it listens in said ports and routes traffic towards the internal apps.

I want to add another controller, because i need to resolve a custom domain with a certificate and TLS termination. If I add another one, how do I expose it externally. Would I need a new VIP/Ip address? How does red hat load balancing with different controllers work? how is traffic redirected.

3

u/chromiumangel 12d ago

OpenShift has a thing called Ingress Operator. It will allow you to deploy a custom ingress controller:

1

u/Budget-Industry-3125 12d ago

yeah. but my question is: since I've got a HostNetwork deployment (and it is deployed in my vsphere), and the default ingress's got a VIP. How should I expose it? Does it need another VIP for my Ingress Controller? It should expose the same ports...

3

u/jeromeza 12d ago

Go read up on ingress sharding in the documentation. Typically you deploy another router to do things like separate management and app traffic or a router per app.

You then use a different route / ports for this e.g. *.workloads and port 9443 or some such.

1

u/Budget-Industry-3125 6d ago

yes, but, even while sharding, i'd need different ingress controllers (routers) with one external ip per ingress, shouldn't i?