shellcheck image is hosted in a VMware-owned registry

[sbueringer]

Hey folks,

just wanted to let you know that the shellcheck image used (gcr.io/cluster-api-provider-vsphere/extra/shellcheck) is hosted in a VMware-owned registry (/ GCP project). In CAPV we replaced usage of the image through a script (https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/hack/verify-shellcheck.sh). I would highly recommend also migrating to the script.

We won't delete the image from the current registry, but we also cannot guarantee that it will exist forever there.

[XudongLiuHarold]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten