Skip to content
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

Fix net_ipv4_ip_local_port_range_max range for azurerm_kubernetes_cluster default node pool #12859

Merged
merged 3 commits into from
Aug 5, 2021
Merged

Conversation

heoelri
Copy link
Contributor

@heoelri heoelri commented Aug 5, 2021

Adjusting ValidateFunc for net_ipv4_ip_local_port_range_max from IntBetween(1024, 60999) to IntBetween(32768, 65000) based on the documentation here: https://docs.microsoft.com/en-us/azure/aks/custom-node-configuration#socket-and-network-tuning

image

This was raised in issue #12483 by @Ledermayer

+adding sensitive = true in the kubernetes docs example. To avoid an error when using the example definition:

image

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @heoelri - LGTM ❄️

@github-actions
Copy link

github-actions bot commented Aug 6, 2021

This functionality has been released in v2.71.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Sep 6, 2021

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants