Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
LoadBalancer vs NodePort with manualy setup LB (haproxy.cfg difference) #867
Ok. So i have set type LoadBalancer and it works. I decided to setup TCP LoadBalancer on Azure by myself instead of leaving it to Kubernetes so i Created my own LB which works and switched voyager ingress anotation to NodePort and backends to use 31443 nodeport.
And i expected it to work the same. But im getting.
from voyagers haproxy
So my request is basicly to https://api.mydomain.com (443 of course)
becomes this (up is LoadBalancer type, down is NodePort type)
with addition of
when nodeport used
backend config have this
Any ideas how to make it work same with NodePort. That is to generate same config as on LoadBalalncer type.
It seems to work with if i send header "Host:api.mydomain.com:31443".
This should answer your question.
made it work. I was searching docs for something similar but finding 'terms' for relevant thing is not always simple task.
I did also looked for all supported annotations here:
and its not mentioned. But big thanks.
@KresoDenis , glad that you got it to work. In 6.0.0-rc.0 release, we have reversed the behavior and it is documented here: https://appscode.com/products/voyager/6.0.0-rc.0/concepts/ingress-types/nodeport/#understanding-ingress-appscode-com-use-node-port-annotation
Regarding search, I am looking for a better /easy to use search engine tool. Finding stuff is difficult as-is . :(