Modernize terraform config for self-hosted runners

[shunping]

Changes

• Upgraded syntax. (Tested with the latest Terraform v1.14.2)
• Upgraded provider version.
• Added documentation

References

• https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release
• Error / issue applying kubelet config terraform-google-modules/terraform-google-kubernetes-engine#2014
• https://developer.hashicorp.com/terraform/language/syntax/configuration
• https://developer.hashicorp.com/terraform/plugin/sdkv2/guides/terraform-0.12-compatibility

---

follow-up #37116
fixes #37115

[gemini-code-assist]

Summary of Changes

Hello @shunping, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on modernizing the Terraform configuration for self-hosted GitHub Actions runners. It updates the syntax for Helm release value assignments, upgrades the Google Terraform provider to a newer version, and significantly improves the documentation by adding a comprehensive guide for updating the configuration. These changes aim to enhance the maintainability, clarity, and future-proofing of the infrastructure code.

Highlights

• Terraform Syntax Modernization: The configuration for Helm releases has been updated to use a more modern list-of-maps syntax for setting values, replacing the older dynamic block approach.
• Google Provider Upgrade: The Google Terraform provider has been upgraded to version ~> 6.7.0, ensuring compatibility with the latest features and improvements.
• Enhanced Documentation: New documentation has been added to the README, providing clear, step-by-step instructions on how to update the Terraform configuration for self-hosted runners.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[shunping]

I also ran the commands documented in the README to deploy a new runner image to gke.

Now the latest runner image 2.330.0 is already in effect.

[shunping]

r: @damccorm @Abacn @Amar3tto

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[shunping]

Watching workflows:

• main pool: https://github.com/apache/beam/actions/workflows/beam_PreCommit_Python.yml
  • successful run: https://github.com/apache/beam/actions/runs/20290651502
• highmem pool: https://github.com/apache/beam/actions/workflows/beam_PostCommit_Python_Examples_Flink.yml
  • successful run: https://github.com/apache/beam/actions/runs/20285675029