fix: (IAC-1072) Enabling North-South traffic #341
Merged
Conversation
This file contains 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.
Changes:
Starting Kubernetes version
1.25the north-south traffic in Azure stopped working. There were no changes toazure-ip-masq-agentorcoredns. On investigating further found out that changes were made to Azure's standard Loadbalancer. See the following note in AKS public standard load balancer documentationTo enable the North-South traffic again for AKS clusters, adding the
aks_pod_cidrto terraform output for viya4-deployment to consume the changes.Tests:
Verified
aks_pod_cidrwas included in terraform.tfstate file