@@ -10,7 +10,7 @@ weight: 200
10
10
11
11
{{< feature-state feature_gate_name="CoordinatedLeaderElection" >}}
12
12
13
- Kubernetes {{< skew currentVersion >}} includes an alpha feature that allows {{<
13
+ Kubernetes {{< skew currentVersion >}} includes a beta feature that allows {{<
14
14
glossary_tooltip text="control plane" term_id="control-plane" >}} components to
15
15
deterministically select a leader via _ coordinated leader election_ .
16
16
This is useful to satisfy Kubernetes version skew constraints during cluster upgrades.
@@ -23,15 +23,16 @@ version, followed by creation timestamp.
23
23
Ensure that ` CoordinatedLeaderElection ` [ feature
24
24
gate] ( /docs/reference/command-line-tools-reference/feature-gates/ ) is enabled
25
25
when you start the {{< glossary_tooltip text="API Server"
26
- term_id="kube-apiserver" >}}: and that the ` coordination.k8s.io/v1alpha1 ` API group is
26
+ term_id="kube-apiserver" >}}: and that the ` coordination.k8s.io/v1beta1 ` API group is
27
27
enabled.
28
28
29
29
This can be done by setting flags ` --feature-gates="CoordinatedLeaderElection=true" ` and
30
- ` --runtime-config="coordination.k8s.io/v1alpha1 =true" ` .
30
+ ` --runtime-config="coordination.k8s.io/v1beta1 =true" ` .
31
31
32
32
## Component configuration
33
+
33
34
Provided that you have enabled the ` CoordinatedLeaderElection ` feature gate _ and_
34
- have the ` coordination.k8s.io/v1alpha1 ` API group enabled, compatible control plane
35
+ have the ` coordination.k8s.io/v1beta1 ` API group enabled, compatible control plane
35
36
components automatically use the LeaseCandidate and Lease APIs to elect a leader
36
37
as needed.
37
38
0 commit comments