You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2019. It is now read-only.
Spending more time thinking about this, I'm not sure if I can do TCP load balancing based on the hostname affiliated with the ingress without having a new public IP for each hostname.
I'm very uncertain what's feasible here.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to support Windows agents and Azure Container Instances, it appears that we need to punch port 50000 through the Kubernetes ingresses
womp womp
The text was updated successfully, but these errors were encountered: