vSphere CCM and CSI components fail to pull their images from gcr.io/cloud-provider-vsphere

[embik]

What happened?

vSphere clusters fail to pull container images for CCM and CSI components, so CSI and CCM Pods fail to start. These images were all hosted in ghcr.io/cloud-provider-vsphere, which has apparently been deleted in the last few hours:

$ skopeo inspect docker://gcr.io/cloud-provider-vsphere/csi/release/driver:v3.3.1
FATA[0000] Error parsing image name "docker://gcr.io/cloud-provider-vsphere/csi/release/driver:v3.3.1": unable to retrieve auth token: invalid username/password: denied: Project cloud-provider-vsphere has been deleted.

While CCM has a new location (see https://github.com/kubernetes/cloud-provider-vsphere?tab=readme-ov-file#container-images), CSI drivers were never published to another registry.

Expected behavior

vSphere clusters work.

How to reproduce the issue?

• Create or upgrade any vSphere cluster.
• Add new machines to a vSphere cluster.

What KubeOne version are you using?

All releases are affected.

Provide your KubeOneCluster manifest here (if applicable)

# paste manifest here

What cloud provider are you running on?

vSphere

What operating system are you running in your cluster?

N/A

Additional information

The same issue exists in KKP at kubermatic/kubermatic#13719.

[embik]

This has been fixed in the PRs referenced above. Patch releases are available:

• v1.7.6
• v1.8.3

If you are affected by this bug, please upgrade to the latest patch releases of your respective release series.

I will go ahead and close this issue since it's been resolved and new releases are available, but it will probably stay pinned to the repository for a little while longer to ensure it's visibile.

/close

[kubermatic-bot]

@embik: Closing this issue.

In response to this:

This has been fixed in the PRs referenced above. Patch releases are available:

• v1.7.6
• v1.8.3

If you are affected by this bug, please upgrade to the latest patch releases of your respective release series.

I will go ahead and close this issue since it's been resolved and new releases are available, but it will probably stay pinned to the repository for a little while longer to ensure it's visibile.

/close

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.