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
After Upgrading to k8S 1.25, Cluster to cluster communication is now using the private networking somehow. Is that expected?We're not sure why it changed or how it's working? Public DNS has a public IP. Checking DNS from within pods shows a public IP. So Azure and/or k8s is translating it magically somewhere. I need help figure out how?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After Upgrading to k8S 1.25, Cluster to cluster communication is now using the private networking somehow. Is that expected?We're not sure why it changed or how it's working? Public DNS has a public IP. Checking DNS from within pods shows a public IP. So Azure and/or k8s is translating it magically somewhere. I need help figure out how?
Beta Was this translation helpful? Give feedback.
All reactions