v0.13.1

🐛 Bug Fixes

fix: VPC NAT Port Range min/max values @brent-anyscale (#24)

Update to VPC NAT Configuration if using Private Networking. GCP Dynamic Port Allocation causes problems with advanced Anyscale Network cluster startup processes. Disabling Dynamic Port Allocation and manually setting min/max ports per VM solves this. Added two new variables to the google-anyscale-vpc sub-module to support this configuration. Changed the minimum ports per VM to 32 from 64.

Fixes #23

On branch brent/vpc-natport
Changes to be committed:
modified: CHANGELOG.md
modified: modules/google-anyscale-vpc/README.md
modified: modules/google-anyscale-vpc/nat.tf
modified: modules/google-anyscale-vpc/variables.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No