we have our AKS running in a private VNET, behind a corporate proxy. The proxy is not a "transparent" proxy and needs to be configured manually an all nodes. Is this a supported behavior? Is it possible to configure worker nodes and all system containers to work via proxy?
相关问题
- unable to access DB pod External IP from applicati
- Get all `Facets` from azure search without item re
- Azure: Microsoft.Compute resource provider stuck &
- Pull image from and connect to the ACS Engine Kube
- How to create a docker-compose.yml file with both
相关文章
- Azure: Microsoft.Compute resource provider stuck &
- 我怎样才能在Azure的集装箱注册表从逻辑应用程序认证(How can I authenticate
- Azure的云应用程序ERR_CONNECTION_TIMED_OUT(Azure Cloud Ap
- Pull image from and connect to the ACS Engine Kube
- How to create a docker-compose.yml file with both
- Managed Azure Kubernetes connection error
- Azure Cloud App ERR_CONNECTION_TIMED_OUT
- AKS in a private VNET behind a corporate proxy
Actually, Azure Kubernetes managed by Azure and in a private Vnet create yourself or Azure. You can use the Load Balancer to transfer the traffic or use ingress. But you just can select one size and type for the nodes when you create the cluster and it seems not support multi size for the nodes currently. Maybe it will be supported in the future on Azure.
For more details about AKS, see Azure Kubernetes Service.