🌱 hack: remove references to GCR_KEY_FILE

[chrischdi]

What this PR does / why we need it:

Follow-up to #2955

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[chrischdi]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.10

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-sigs/prow repository.

[chrischdi]

/cherry-pick release-1.9

[k8s-infra-cherrypick-robot]

@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.9

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-sigs/prow repository.

[chrischdi]

/test help

[k8s-ci-robot]

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-29-1-30-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-29-1-30-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main
• /test pull-cluster-api-provider-vsphere-test-main
• /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-vsphere-apidiff-main

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-vsphere-apidiff-main
• pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• pull-cluster-api-provider-vsphere-test-main
• pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test help

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-sigs/prow repository.

[chrischdi]

/test pull-cluster-api-provider-vsphere-e2e-govmomi-main

[sbueringer]

/lgtm
/approve

I assume we do the corresponding cleanup in test-infra. I assume we don't have to care about actually deleting the secret in the Prow cluster as we can just invalidate it by maybe removing the corresponding service account? (or the credential)

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b9ee2962c98b06fe6aadb07b19b0b5ff23920a5b

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #2994

In response to this:

/cherry-pick release-1.10

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@chrischdi: #2990 failed to apply on top of branch "release-1.9":

Applying: hack: remove references to GCR_KEY_FILE
Using index info to reconstruct a base tree...
M	hack/e2e.sh
Falling back to patching base and 3-way merge...
Auto-merging hack/e2e.sh
CONFLICT (content): Merge conflict in hack/e2e.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 hack: remove references to GCR_KEY_FILE
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.9

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-sigs/prow repository.