Bump Kubernetes to v1.27.1 in management cluster

[electrocucaracha]

It seems like Porch has some race conditions in older Kubernetes versions, this is an attempt to mitigate them.

[johnbelamaric]

The race is in k8s API server CRD handling when two CRDs are registered with the same resource name (I think).

This may or may not fix it. A more assured fix would be to use the "cl" name for CAPI clusters rather than the full "clusters" name which seems to be shared with clusterregistry.

Either that, or see if maybe clusterregistry API resource doesn't exist in the older (or this newer) kind version. I don't know if that's used by CAPI or what.

[johnbelamaric]

#153

Should fix the issue I am seeing for the tests failing due to timeouts waiting for clusters to be ready.

To fix the fragment issue - which is a known flake, not something that always happens - we need kptdev/kpt#3993. I do not think we need to wait for that for tagging our release.

[johnbelamaric]

Flake: Error: the server is currently unable to handle the request (get packagerevisions.porch.kpt.dev)

This is a different issue than the fragment issue, but also a flake.

/retest

[radoslawc]

/approve
/lgtm

[nephio-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: electrocucaracha, radoslawc

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

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

[electrocucaracha]

/retest