[release-1.10] 🐛 Fix pattern on Cluster classNamespace field

[sbueringer]

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

What this PR does / why we need it:

Validation was wrong because it validated the field for being a subdomain, but it is DNS1123Subdomain instead.

xref: partial cherry-pick from #12235

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-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-10

/test pull-cluster-api-e2e-blocking-release-1-10

/test pull-cluster-api-e2e-conformance-ci-latest-release-1-10

/test pull-cluster-api-e2e-conformance-release-1-10

/test pull-cluster-api-e2e-mink8s-release-1-10

/test pull-cluster-api-e2e-release-1-10

/test pull-cluster-api-e2e-upgrade-1-32-1-33-release-1-10

/test pull-cluster-api-test-mink8s-release-1-10

/test pull-cluster-api-test-release-1-10

/test pull-cluster-api-verify-release-1-10

The following commands are available to trigger optional jobs:

/test pull-cluster-api-apidiff-release-1-10

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

pull-cluster-api-apidiff-release-1-10

pull-cluster-api-build-release-1-10

pull-cluster-api-e2e-blocking-release-1-10

pull-cluster-api-test-release-1-10

pull-cluster-api-verify-release-1-10

In response to this:

/test pull-cluster-api-e2e-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-sigs/prow repository.

[sbueringer]

/assign @fabriziopandini @JoelSpeed

Would be good to merge ASAP so we can include it in the patch release today

[JoelSpeed]

/lgtm
/approve

I don't think I'm an owner on this branch 🤔

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 57de9ca6b6aeb04f5990eb57d484a0e464e74a81

[sbueringer]

/lgtm /approve

I don't think I'm an owner on this branch 🤔

Ah yes, good point I forgot

In general I would recommed to go through the PRs that have been linked here (#9997) post merge and open a few PRs to ensure you have the right permissions everywhere

[chrischdi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi, JoelSpeed

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 [chrischdi]

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

[JoelSpeed]

In general I would recommed to go through the PRs that have been linked here (#9997) post merge and open a few PRs to ensure you have the right permissions everywhere

Will do