Skip to content

Commit c68450c

Browse files
Apply suggestions from code review
Co-authored-by: Craig Shoemaker <[email protected]>
1 parent bf4d167 commit c68450c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/health-probes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,9 +170,9 @@ If ingress is enabled, the following default probes are automatically added to t
170170
| Liveness | Protocol: TCP<br>Port: ingress target port |
171171
| Readiness | Protocol: TCP<br>Port: ingress target port<br>Timeout: 5 seconds<br>Period: 5 seconds<br>Initial delay: 3 seconds<br>Success threshold: 1<br>Failure threshold: 48 |
172172

173-
If you're running your container app in [multiple revision mode](revisions.md#revision-modes), after you deploy a revision, you should wait until your readiness probes indicate success before you shift traffic to that revision. In single revision mode, this happens automatically (that is, traffic is not shifted to the new revision until its readiness probes indicate success.)
173+
If you're running your container app in [multiple revision mode](revisions.md#revision-modes), after you deploy a revision, wait until your readiness probes indicate success before you shift traffic to that revision. In single revision mode, traffic is shifted automatically once the readiness probe returns a successful state.
174174

175-
A revision state appears as unhealthy if any of its replicas fails its readiness probe check, even if all other replicas in the revision are healthy. Container Apps restarts the replica in question until it is healthy again or the failure threshold is exceeded. If the failure threshold is exceeded, it might help to restart the revision, but it might also mean the revision is not configured correctly.
175+
A revision state appears as unhealthy if any of its replicas fails its readiness probe check, even if all other replicas in the revision are healthy. Container Apps restarts the replica in question until it is healthy again or the failure threshold is exceeded. If the failure threshold is exceeded, try restarting the revision, but it might mean the revision is not configured correctly.
176176

177177
If your app takes an extended amount of time to start (which is common in Java) you often need to customize the probes so your container doesn't crash.
178178

0 commit comments

Comments
 (0)