thanks for your prompt response, i did read through this thread prior and it does relate to my understanding of the issue. it seems like we could 1) use ips instead of host names, not ideal due to the dynamic nature of the ips 2) maintain an upstream configuration externally and use nginx reload to modify the upstream as pods come online scaling up, as stated in the referenced threadby kpirateone - Nginx Mailing List - English
I am trying to configure a least_conn upstream for kubernetes pods and find that we receive a "host not found in upstream" error on startup if the pod has not been started. config snippet: upstream backend { least_conn; server pod0.servicename.namespace.svc.cluster.local:8081; server pod1.servicename.namespace.svc.cluster.local:8081; serverby kpirateone - Nginx Mailing List - English