terraform, gcp: add opt-out var to collaboratively and opportunistically apply node-purpose infra labels #3406
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is for #3405, a followup to #3397 that is work I think all @2i2c-org/engineering needs to opportunistically apply over time when given the chance. @2i2c-org/engineering the ask is that when you apply terraform config, consider if there are a fixme that you'd like to opportunistically resolve while you are at it.
This PR adds variables and fixme notes in individual GCP clusters' .tfvar files, allowing us to see where we haven't yet managed to apply what #3397 introduced.
The purpose of this is to: