feat(azure): Set defaults for production AKS#469
Merged
Conversation
- Update AKS service_cidr to 10.0.0.0/16 and dns_service_ip to 10.0.0.10 - Simplify network config structure in AKS module - Fix test assertions for VNet address_space and subnet structure - Add context_id to network configuration tests - Update subnet object structure in VNet tests
- Update documentation for Azure AKS and VNet modules - Add Azure example context - Update Talos and Nginx configurations - Add AKS module README
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
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.
A few light enhancements to improve things when performing
windsor up --wait+windsor downagainst a production grade cluster. These changes make sure the defaults are sufficient for a standard blueprint deployment.IP range change:
Other changes:
windsor initgenerated assets