[WIP] Fix waiting for all pods having specified labels to be Ready

[prezha]

fixes #19288

this pr ensures that, when requested (via --wait flag), we wait until all (at least one) pods that have one of the CorePodsLabels in the kube-system namespace to be "Ready" or timeout

---

note: this pr should be merged after #20313 (and then rebase, solving expected conflicts)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: prezha

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

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

[prezha]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20315) |
+----------------+----------+---------------------+
| minikube start | 48.4s    | 49.2s               |
| enable ingress | 14.6s    | 15.1s               |
+----------------+----------+---------------------+

Times for minikube start: 46.2s 50.3s 47.6s 49.4s 48.5s
Times for minikube (PR 20315) start: 49.6s 48.0s 50.6s 49.8s 48.1s

Times for minikube ingress: 14.4s 14.5s 14.9s 14.4s 14.9s
Times for minikube (PR 20315) ingress: 14.9s 14.9s 14.9s 15.9s 14.9s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20315) |
+----------------+----------+---------------------+
| minikube start | 22.1s    | 21.5s               |
| enable ingress | 12.9s    | 12.4s               |
+----------------+----------+---------------------+

Times for minikube start: 23.9s 24.0s 20.2s 19.9s 22.7s
Times for minikube (PR 20315) start: 23.3s 20.2s 19.8s 20.2s 24.0s

Times for minikube ingress: 12.8s 12.7s 13.2s 12.7s 13.2s
Times for minikube (PR 20315) ingress: 12.2s 12.2s 12.7s 12.2s 12.7s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20315) |
+----------------+----------+---------------------+
| minikube start | 22.5s    | 21.9s               |
| enable ingress | 39.1s    | 39.0s               |
+----------------+----------+---------------------+

Times for minikube start: 21.6s 22.7s 23.0s 22.6s 22.7s
Times for minikube (PR 20315) start: 19.1s 23.3s 22.3s 22.6s 22.3s

Times for minikube ingress: 39.2s 39.2s 38.8s 39.2s 39.2s
Times for minikube (PR 20315) ingress: 38.7s 38.8s 39.3s 39.2s 39.2s

[minikube-pr-bot]

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate
Docker_Linux (2 failed)	TestFunctional/parallel/MountCmd/specific-port(gopogh)	0.00% (chart)
Docker_Linux (2 failed)	TestMultiNode/serial/RestartMultiNode(gopogh)	0.00% (chart)
Docker_Linux_containerd_arm64 (1 failed)	TestScheduledStopUnix(gopogh)	9.80% (chart)
Docker_Linux_crio_arm64 (3 failed)	TestScheduledStopUnix(gopogh)	5.88% (chart)
Docker_Linux_crio_arm64 (3 failed)	TestFunctional/parallel/PersistentVolumeClaim(gopogh)	10.87% (chart)

Besides the following environments also have failed tests:

• Docker_Cloud_Shell: 3 failed (gopogh)

• KVM_Linux_crio: 10 failed (gopogh)

• Docker_Linux_containerd: 18 failed (gopogh)

• Docker_Linux_crio: 15 failed (gopogh)

To see the flake rates of all tests by environment, click here.