Currently the workload controller uses its service name (wkldcontroller) to contact the stats service, which runs in the same container. However, some Kubernetes networking providers do not allow traffic to hairpin to the source pod through its own service. This prevents the workload controller from starting.
This change has the workload controller contact the stats service via the localhost hostname. A separate workloadStatsHostname is used for the driver nodes so that they can still contact the stats service using the wkldcontroller service.
Currently the workload controller uses its service name (wkldcontroller) to contact the stats service, which runs in the same container. However, some Kubernetes networking providers do not allow traffic to hairpin to the source pod through its own service. This prevents the workload controller from starting.
This change has the workload controller contact the stats service via the localhost hostname. A separate workloadStatsHostname is used for the driver nodes so that they can still contact the stats service using the wkldcontroller service.