Automated cherry pick of #49125

[abgworrall]

When testing, GKE created clusters don't provide a MasterName, so carry on anyway and log node OS images without it

Background: this is code that runs during gce/gke testing, and records which specific OS images were being run on the master and node. When we test new OS images for GKE, we need to test them on all supported branches (i.e. >=1.5), so this piece of work needs to be backported to all branches. This specific cherrypick adds a guard for GKE-created clusters, which omit the MasterName, letting it proceed and log the node OS.

Cherry pick of #49125 on release-1.6.

#49125: Tolerate a missing MasterName (for GKE)

[k8s-ci-robot]

Hi @abgworrall. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-github-robot]

The 'parent' PR of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement. (release-note-experimental must be explicit for cherry-picks)

[sttts]

/unassign

[rmmh]

/lgtm

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: abgworrall, rmmh
We suggest the following additional approver: kow3ns

Assign the PR to them by writing /assign @kow3ns in a comment when ready.

Associated issue: 49125

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• test/OWNERS

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[abgworrall]

/test pull-kubernetes-e2e-gce-etcd3

[k8s-ci-robot]

@abgworrall: you can't request testing unless you are a kubernetes member.

In response to this:

/test pull-kubernetes-e2e-gce-etcd3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[abgworrall]

/assign @zmerlynn
Hi, Zach - first of three backports of this change, to all the branches. If you can give me an ok-to-test, I'll start playing the pull-kubernetes-e2e-gce-etcd3 lottery :)

[enisoc]

/ok-to-test

[k8s-github-robot]

Automatic merge from submit-queue