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
This commit is contained in:
		
							parent
							
								
									0cac8d21c4
								
							
						
					
					
						commit
						434469c084
					
				| 
						 | 
				
			
			@ -96,10 +96,10 @@ Services will always have the `ready` condition set to `true`.
 | 
			
		|||
 | 
			
		||||
#### Serving
 | 
			
		||||
 | 
			
		||||
{{< feature-state for_k8s_version="v1.22" state="beta" >}}
 | 
			
		||||
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
 | 
			
		||||
 | 
			
		||||
`serving` is identical to the `ready` condition, except it does not account for terminating states.
 | 
			
		||||
Consumers of the EndpointSlice API should check this condition if they care about pod readiness while
 | 
			
		||||
The `serving` condition is almost identical to the `ready` condition. The difference is that
 | 
			
		||||
consumers of the EndpointSlice API should check the `serving` condition if they care about pod readiness while
 | 
			
		||||
the pod is also terminating.
 | 
			
		||||
 | 
			
		||||
{{< note >}}
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue