Skip to content

Releases: BrownUniversity/terraform-gcp-cluster

v0.1.11 🌈

09 Jan 18:33
14c664e
Compare
Choose a tag to compare

Changes

v0.1.10 🌈

07 Jan 20:43
f544db1
Compare
Choose a tag to compare

Changes

v0.1.9 🌈

15 Aug 14:53
e93e1a5
Compare
Choose a tag to compare

Changes

🧰 Maintenance

v0.1.8 🌈

31 Jul 15:19
b0a5c43
Compare
Choose a tag to compare

Changes

🧰 Maintenance

v0.1.7 🌈

29 Jul 18:30
50c46df
Compare
Choose a tag to compare

Changes

🧰 Maintenance

v0.1.6 🌈

19 Jul 13:45
c6b2df2
Compare
Choose a tag to compare

Changes

🧰 Maintenance

v0.1.5 🌈

11 Jan 22:11
0098d6e
Compare
Choose a tag to compare

Changes

Enabling this makes standard_rwo storage class available, which resolves standard volumes from not binding, possibly due to a timing issue. For ClassStorage standard volumeBindingMode: Immediate for standard_rwo -> volumeBindingMode: WaitForFirstConsumer
See more https://stackoverflow.com/questions/72553227/gke-can-t-scale-up-nodes-due-of-persistentvolume

  • chore: adds release_channel as a variable and sets it to REGULAR this should help make k8s versions a little more stable.

v0.1.4 🌈

23 Aug 15:14
1657b70
Compare
Choose a tag to compare

Changes

🧰 Maintenance

Update versions @mirestrepo (#15) in particular, it updates:

  • Terraform
  • Ruby
  • Providers
  • Modules in GitHub Actions
  • Use org secrets instead of local
  • Use official docker build/push action instead of manual steps
  • Transition to COS_CONTAINERD

v0.1.3 🌈

15 Jul 20:12
347da88
Compare
Choose a tag to compare

Changes

This release makes the GKE cluster get provisioned with a super-specific version of 1.22 and the last version of the Google provider that supports versions less than v4.0.0 (the last one that still supports docker engine rather than container.d. This is likely unsustainable, but will likely be resolved in a v0.1.4 release.

🐛 Bug Fixes

  • Call specific GKE version in release channel @broestls (#13)

v0.1.2 🌈

06 Jun 01:33
091826a
Compare
Choose a tag to compare

Changes

🐛 Bug Fixes