Fix net_ipv4_ip_local_port_range_max
range for azurerm_kubernetes_cluster
default node pool
#12859
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.
Adjusting
ValidateFunc
fornet_ipv4_ip_local_port_range_max
fromIntBetween(1024, 60999)
toIntBetween(32768, 65000)
based on the documentation here: https://docs.microsoft.com/en-us/azure/aks/custom-node-configuration#socket-and-network-tuningThis was raised in issue #12483 by @Ledermayer
+adding
sensitive = true
in the kubernetes docs example. To avoid an error when using the example definition: