99f7df3e1c
The default service-cidr controller blocks the apiserver because it needs to create the default ServiceCIDR so Services can be allocated. If the apiserver is started without the default ServiceCIDR any attempt to createa new Service will fail, and this is a breaking change for users and installers that does not retry on this operation. Instead of using a channel to signal the controller is ready, just implement two loops, a first one that verifies that is ready and that polls with a shorted interval, and leave the second loop with the existing interval. Change-Id: I54303af9faeaa9c5cce2a840b6b7b0320cd2f4ad |
||
|---|---|---|
| .. | ||
| apiserverleasegc | ||
| clusterauthenticationtrust | ||
| crdregistration | ||
| defaultservicecidr | ||
| kubernetesservice | ||
| legacytokentracking | ||
| systemnamespaces | ||