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 24, 2023. It is now read-only.
I have a Windows Kubenetes ACS cluster. I am using VNET peering in order to allow the cluster to reach out to our internal resources. When I try to scale the cluster with the VNET peerings in place, I get the error in the screenshot below.
I removed the VNET peerings and the cluster was able to expand the number of agents. Then I added the peering back.
The text was updated successfully, but these errors were encountered:
VNET peering is not currently supported in ACS. To do VNET peering the suggested path is to use ACS-Engine . We are working on adding VNET peering as a supported scenario in ACS but do not have an ETA and I wouldn't expect it soon. Hope this helps.
Make sure to read some of the Github issues around peering VNETs. There are some manual steps that aren't immediately obvious. The one I am thinking of is you need to masquerade the k8s route table into the peered network, if I have the wording right I'm not an expert on this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a Windows Kubenetes ACS cluster. I am using VNET peering in order to allow the cluster to reach out to our internal resources. When I try to scale the cluster with the VNET peerings in place, I get the error in the screenshot below.
I removed the VNET peerings and the cluster was able to expand the number of agents. Then I added the peering back.
The text was updated successfully, but these errors were encountered: