[release-1.2] ⚠️ KCP: block upgrade to versions with old registry, improve registry handling

[sbueringer]

handling

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
Manual cherry-pick of #7856

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 #

[sbueringer]

/test pull-cluster-api-e2e-full-main
/test pull-cluster-api-e2e-workload-upgrade-1-25-latest-main

[k8s-ci-robot]

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

• /test pull-cluster-api-build-release-1-2
• /test pull-cluster-api-e2e-release-1-2
• /test pull-cluster-api-test-mink8s-release-1-2
• /test pull-cluster-api-test-release-1-2
• /test pull-cluster-api-verify-release-1-2

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-apidiff-release-1-2
• /test pull-cluster-api-e2e-full-release-1-2
• /test pull-cluster-api-e2e-informing-ipv6-release-1-2
• /test pull-cluster-api-e2e-informing-release-1-2
• /test pull-cluster-api-e2e-workload-upgrade-1-25-latest-release-1-2

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

• pull-cluster-api-apidiff-release-1-2
• pull-cluster-api-build-release-1-2
• pull-cluster-api-e2e-informing-ipv6-release-1-2
• pull-cluster-api-e2e-informing-release-1-2
• pull-cluster-api-e2e-release-1-2
• pull-cluster-api-test-mink8s-release-1-2
• pull-cluster-api-test-release-1-2
• pull-cluster-api-verify-release-1-2

In response to this:

/test pull-cluster-api-e2e-full-main
/test pull-cluster-api-e2e-workload-upgrade-1-25-latest-main

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.

[sbueringer]

/test pull-cluster-api-e2e-workload-upgrade-1-25-latest-release-1-2

[sbueringer]

/test pull-cluster-api-e2e-full-release-1-2

[sbueringer]

cc @fabriziopandini

[sbueringer]

/retest

I'll try to reproduce locally in parallel

[sbueringer]

I think it's a flake. Looks like a kube-apiserver Pod didn't come up for some reason. On my machine the same test was green

[sbueringer]

/retest

[sbueringer]

/test pull-cluster-api-e2e-workload-upgrade-1-25-latest-release-1-2
/test pull-cluster-api-e2e-full-release-1-2

[sbueringer]

/test pull-cluster-api-e2e-full-release-1-2

[sbueringer]

/lgtm
/approve

[k8s-ci-robot]

@sbueringer: you cannot LGTM your own PR.

In response to this:

/lgtm
/approve

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.

[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

[killianmuldoon]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f67d8c36fc5c4f172dd4e269bb84ac695b8c0581