Skip to content

Commit db8ca26

Browse files
authored
Merge pull request #35632 from Shubham82/update_feature_state_EndpointSliceTerminatingCondition
Updated the Feature state of Serving and Terminating.
2 parents e66d7a4 + 9a45975 commit db8ca26

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/concepts/services-networking/endpoint-slices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ Services will always have the `ready` condition set to `true`.
108108

109109
#### Serving
110110

111-
{{< feature-state for_k8s_version="v1.20" state="alpha" >}}
111+
{{< feature-state for_k8s_version="v1.22" state="beta" >}}
112112

113113
`serving` is identical to the `ready` condition, except it does not account for terminating states.
114114
Consumers of the EndpointSlice API should check this condition if they care about pod readiness while
@@ -127,7 +127,7 @@ for terminating pods independent of the existing semantics for `ready`.
127127

128128
#### Terminating
129129

130-
{{< feature-state for_k8s_version="v1.20" state="alpha" >}}
130+
{{< feature-state for_k8s_version="v1.22" state="beta" >}}
131131

132132
`Terminating` is a condition that indicates whether an endpoint is terminating.
133133
For pods, this is any pod that has a deletion timestamp set.

0 commit comments

Comments
 (0)