4a223efd27
Automatic merge from submit-queue Test API more extensivelly before declaring readiness **What this PR does / why we need it**: It's possible that first deployment kubeadm creates will hit `deployments.extensions "kube-discovery" is forbidden: not yet ready to handle request`, which comes from NamespaceLifecycle admission controller and has something to do with cache. According to @derekwaynecarr, we need to create a namespace-scoped resource to really check for this. I didn't want to make a check with deployment of whatever comes first right now, and decided to have explicit step for this in `apiclient.go`. **Which issue this PR fixes**: fixes #34411 **Special notes for your reviewer**: @kubernetes/sig-cluster-lifecycle **Release note**: ```release-note NONE ``` |
||
|---|---|---|
| .. | ||
| addons.go | ||
| apiclient.go | ||
| discovery.go | ||
| kubeconfig.go | ||
| manifests.go | ||
| pki.go | ||
| tokens.go | ||