Replies: 1 comment
-
I have gotten around this by setting up an external load balancer on my network (HAProxy) which seems to work fine. Perhaps I was overthinking the setup, maybe it's not possible to have an Ingress listen on an IP provided by MetalLB? Now my setup is: HAProxy distributes traffic to my 3x nodes --> Ingress listening for requests to https://dns.my.domain --> Ingress points to pinhole-web (now set up as a ClusterIP) DNS Service is still running with the MetalLB-assigned IP address to keep that static. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am a little new to Kubernetes so apologies if this is basic but hoping someone can help. I have recently been playing around with this Helm chart and have gotten everything working.
My setup:
I followed the documentation on here and a few other bits I found online. My DNS is responding on 192.168.0.2 and I can also access the web ui on http://192.168.0.2/admin. So far so good!
My question comes to setting up the ingress available in the Helm chart. I have the following:
So if I set my DNS up to point dns.my.domain to one of my nodes (say 192.168.0.11) this works well - I can access https://dns.my.domain/admin and I get my generated SSL certificate securing it.
However, if I instead point dns.my.domain to 192.168.0.2, I cannot access the web UI.
So it seems if I point my DNS to one of the nodes, this all works fine (but this means that it is pointed at a single node which sort of defeats the purpose in my mind of a distributed cluster), should I be able to point my DNS to the IP of my LoadBalancer address (192.168.0.2) and get the same behaviour? Or is there some other config I am missing? Do I need a load balancer external to my Kubernetes cluster for this sort of workflow to work?
Beta Was this translation helpful? Give feedback.
All reactions