Both kubernetes-e2e-gke and kubernetes-e2e-gke-slow have had a couple failures to bring up a cluster this morning, seeing errors like:
Timed out waiting for cluster initialization. Cluster API may not be available.
All cluster resources were brought up, but the cluster API is reporting that component "scheduler" is unhealthy.
@jlowdermilk, does this overlap at all with the investigations you've been doing lately?
Both kubernetes-e2e-gke and kubernetes-e2e-gke-slow have had a couple failures to bring up a cluster this morning, seeing errors like:
Timed out waiting for cluster initialization. Cluster API may not be available.
All cluster resources were brought up, but the cluster API is reporting that component "scheduler" is unhealthy.
@jlowdermilk, does this overlap at all with the investigations you've been doing lately?