tf-modules/gcp/gke: ignore node_config changes #22
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.
When using workload identity in GKE, an empty
node_config.oauth_scopes
is set at provision time. But after the provision, some default scopes are added to the cluster. Reapplying the same config tries to replace the existing scopes with empty scopes. This replacement requires the existing cluster to be deleted and recreated. To avoid cluster recreation between test runs, set a lifecycle rule to ignore any changes in node_config.Encountered this while testing fluxcd/pkg#665 . Was observing the following when rerunning the tests: