Add DelayCacheUntilActive option to start informers after leader election
If scheduler fails to be active (elected if leader election is enabled), setting this option will not start informers so that to avoid memory overhead. Signed-off-by: Eric Lin <exlin@google.com>
This commit is contained in:
7
pkg/generated/openapi/zz_generated.openapi.go
generated
7
pkg/generated/openapi/zz_generated.openapi.go
generated
@@ -54521,6 +54521,13 @@ func schema_k8sio_kube_scheduler_config_v1_KubeSchedulerConfiguration(ref common
|
||||
},
|
||||
},
|
||||
},
|
||||
"delayCacheUntilActive": {
|
||||
SchemaProps: spec.SchemaProps{
|
||||
Description: "DelayCacheUntilActive specifies when to start caching. If this is true and leader election is enabled, the scheduler will wait to fill informer caches until it is the leader. Doing so will have slower failover with the benefit of lower memory overhead while waiting to become leader. Defaults to false.",
|
||||
Type: []string{"boolean"},
|
||||
Format: "",
|
||||
},
|
||||
},
|
||||
},
|
||||
Required: []string{"leaderElection", "clientConnection"},
|
||||
},
|
||||
|
Reference in New Issue
Block a user