GCE: Prefer preconfigured node tags for firewalls, if available

[a-robinson]

It'd be nice to also refactor the way that we use NODE_TAG on the client side in gce/util.sh and NODE_INSTANCE_PREFIX on the server side in gce/configure-vm.sh, but that can be cleaned up separately.

Note that I'm currently waiting on this to build and deploy to verify it works as intended, so it shouldn't be merged until I can confirm that's done.

@roberthbailey @thockin @fabioy

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

[thockin]

LGTM: title is relnote, maybe want to clarify a bit?

[roberthbailey]

lgtm (assuming it passed your manual testing)

[a-robinson]

Just pushed a slight tweak - in the block of env vars in configure-vm.sh that I had set it before, it would only have gotten used on GKE, not on GCE. By separating it out more like the multizone setting it'll also be used on GCE.

With that tweak, I can confirm it works.

[a-robinson]

PTAL, thanks

[a-robinson]

The e2e failures are due to #25153

[k8s-bot]

GCE e2e build/test failed for commit 20699865a6ff994dc4506c779bc6f4f6d5050513.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

[a-robinson]

@K8s e2e test this please issue: #25153

[k8s-bot]

GCE e2e build/test passed for commit b75fa08.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-cherrypick-bot]

Commit found in the "release-1.2" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.