-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Private clusters #486
Comments
/help |
@CecileRobertMichon: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
note: we may need to change https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/controllers/azurecluster_controller.go#L128 to wait for the private IP instead of the DNS name:
|
parity |
@rbitia: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1st step is to define what the implementation would look like /cc @jseely |
/assign |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Support deploying clusters with no public IP or external load balancer. For reference: https://github.com/Azure/aks-engine/blob/master/docs/topics/features.md#feat-private-cluster.
Once Azure Bastion is implemented, we should document using Azure Bastion + Private clusters. related to #165
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: