v0.1.6

📚 Documentation/Examples

upd: Support latest changes for Anyscale Operator on GCP @brent-anyscale (#8)

This matches latest requirements for GKE with recent changes to requirements for the Anyscale Operator.

On branch brent/gke-standard-public
Changes to be committed:
modified: README.md
modified: main.tf
modified: outputs.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

v0.1.5

📚 Documentation/Examples

gke existing cluster: remove var existing_vpc_id and use name to query it @hongchaodeng (#7)

As a follow up for #6 (comment)

Basically We don't need both existing_vpc_name and existing_vpc_id. Can use one to query the other.

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

Other information

v0.1.4

📚 Documentation/Examples

upd: Existing GKE Example @brent-anyscale (#6)

Fixes #5
Additional updates for Helm Chart Ingress sleeps for availability, Job Test python, GCP Storage Bucket permissions, and updates to latest CLI commands.

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

Breaking changes for example. This will recreate some of the resources.

v0.1.3

📚 Examples

Add example for existing GKE cluster @hongchaodeng (#4)

Example terraform.tfvars

google_region     = "..."
google_project_id = "..."

anyscale_deploy_env = "test"
anyscale_org_id     = "..."

existing_vpc_name            = "..."
existing_subnet_name         = "..."
customer_ingress_cidr_ranges = "0.0.0.0/0"

gke_endpoint       = "..."
gke_ca_certificate = "..."

v0.1.2

📚 Documentation/Examples

add: Example for existing GKE cluster - initial commit @brent-anyscale (#3)

Changes to be committed:
new file: README.md
new file: main.tf
new file: outputs.tf
new file: variables.tf
new file: versions.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

Other information

v0.1.1

🐛 Bug Fixes

fix: Tolerances for EKS nodes need to be ON_DEMAND @brent-anyscale (#2)

Switches the ALL tolerance to ON_DEMAND, as taints must be unique to a tuple of (key, effect) in EKS, which wasn't possible with the ALL convention

Changes to be committed:
modified: eks-private/main.tf
modified: eks-public/main.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

v0.1.0

🚀 Initial Release for Kubernetes Anyscale Foundation Modules @brent-anyscale (#1)

Initial PR for v0.0.1 of the Kubernetes Anyscale Foundation Modules