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.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
We have seen that even if we instantiate ACS within our custom VNet/Subnet, it always assigns a Public IP to master node's i.e its load balancer. And there no option to skip it and have only private IP.
What you expected to happen:
We want an option to have only private IP to master nodes.
How to reproduce it (as minimally and precisely as possible):
Create and ACS kubernetes cluster in private subnet.
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
vikaskulwal
changed the title
Feature Request: Option to skip Public IP Master nodes of ACS Kubernetes cluster
Feature Request: Option to skip Public IP for Master nodes of ACS Kubernetes cluster
Nov 21, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
We have seen that even if we instantiate ACS within our custom VNet/Subnet, it always assigns a Public IP to master node's i.e its load balancer. And there no option to skip it and have only private IP.
What you expected to happen:
We want an option to have only private IP to master nodes.
How to reproduce it (as minimally and precisely as possible):
Create and ACS kubernetes cluster in private subnet.
Anything else we need to know:
The text was updated successfully, but these errors were encountered: