aks public cluster with api server vnet integration #110
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jubrad
reviewed
Nov 26, 2025
| address_space = "20.0.0.0/16" | ||
| aks_subnet_cidr = "20.0.0.0/20" | ||
| postgres_subnet_cidr = "20.0.16.0/24" | ||
| enable_api_server_vnet_integration = true |
Collaborator
There was a problem hiding this comment.
This should have a comment about what it does, or a link to the docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The cluster is not private though, if we make the cluster private we would need a bastion host to connect to the cluster from outside of vpc. The current configuration mimics the behaviour of public access + keeping internal aks traffic contained inside vnet. As per internal slack discussion, we don’t want fully private cluster hence the current configuration should work for us. Will raise a pr in sometime for this