https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
it’s a daemonset with hostport 80 and 443, so you can reach the ingress on any of your nodes at 80/443. You can also reach it via the service within the cluster, if you want.
you’d see the hostports if you inspected the pods
l
Aaaah thanks 🙂
Didn't know that Daemonset could configure hostPort directly
c
they’re just pods, you can do anything you can do with a normal pod
l
Didn't know this exist with pod as well to be honest 😅
I learned something, thanks!
p
How would someone recommend routing data to these services then? You obviously don’t want to just point an A Record to a single specific host in case that host goes down for any reason.
c
cnames are an option… or external load-balancers…
if you want to use an in-cluster load-balancer, you can deploy a load-balancer controller and then reconfigure the chart to use LoadBalancer service instead of just ClusterIP
but these are all kind of up to the administrator to decide based on what they have available in their environment
p
gotcha, I think I’d prefer to do LB on the cluster - so would I just remove the current install of NGINX and reinstall with it as a LB?
c
no. ingress-nginx is an ingress controller, not a load-balancer controller
they do different things
l
We do external load balancer indeed
c
load-balancer controllers would be things like kube-vip, metallb, or servicelb
p
Understood.
9 Views
Open in Slack
PreviousNext
Powered by