Skip to content

v0.15.0
Compare
Choose a tag to compare
@github-actions github-actions released this 30 Sep 19:50
· 17 commits to refs/heads/main since this release
v0.15.0
1f28ddb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

🚀 Enhancements

add: Optional VPC Firewall ingress rule for Anyscale Machine Pools @brent-anyscale (#33)

Anyscale Machine Pools requires a specific set of ports to be open from the AMP Node into (ingress) the head node running in the cloud. This update includes an optional parameter ingress_from_machine_pool_cidr_ranges which, when provided, will create a new Firewall Rule allowing the appropriate ports for Anyscale Machine Poolss.

Changes to be committed:
modified: README.md
modified: examples/anyscale-v2-kitchensink/README.md
modified: examples/anyscale-v2-kitchensink/main.tf
modified: main.tf
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc-firewall/examples/main.tf
modified: modules/google-anyscale-vpc-firewall/main.tf
modified: modules/google-anyscale-vpc-firewall/variables.tf
modified: test/test_cloud_register_manual.py
modified: 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

Depending on the Anyscale Firewall currently in place, it may be replaced.

📚 Documentation/Examples

add: Optional VPC Firewall ingress rule for Anyscale Machine Pools @brent-anyscale (#33)

Anyscale Machine Pools requires a specific set of ports to be open from the AMP Node into (ingress) the head node running in the cloud. This update includes an optional parameter ingress_from_machine_pool_cidr_ranges which, when provided, will create a new Firewall Rule allowing the appropriate ports for Anyscale Machine Poolss.

Changes to be committed:
modified: README.md
modified: examples/anyscale-v2-kitchensink/README.md
modified: examples/anyscale-v2-kitchensink/main.tf
modified: main.tf
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc-firewall/examples/main.tf
modified: modules/google-anyscale-vpc-firewall/main.tf
modified: modules/google-anyscale-vpc-firewall/variables.tf
modified: test/test_cloud_register_manual.py
modified: 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

Depending on the Anyscale Firewall currently in place, it may be replaced.

Contributors

brent-anyscale
Assets 2
Loading