Skip to content

Commit 434469c

Browse files
authored
Updated docs for EndpointSliceTerminatingCondition (#38701)
* Rebased issue #38390 * Updated endpoint-slices.md Resolved issue #38701 * Updated endpoint-slice.md * endpoint-slice.md * New endpoint-slice.md file * Updated endpoint-slice.md
1 parent 0cac8d2 commit 434469c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -96,10 +96,10 @@ Services will always have the `ready` condition set to `true`.
9696

9797
#### Serving
9898

99-
{{< feature-state for_k8s_version="v1.22" state="beta" >}}
99+
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
100100

101-
`serving` is identical to the `ready` condition, except it does not account for terminating states.
102-
Consumers of the EndpointSlice API should check this condition if they care about pod readiness while
101+
The `serving` condition is almost identical to the `ready` condition. The difference is that
102+
consumers of the EndpointSlice API should check the `serving` condition if they care about pod readiness while
103103
the pod is also terminating.
104104

105105
{{< note >}}

0 commit comments

Comments
 (0)