Skip to content

Commit 0202264

Browse files
authored
Fix typo in pod readiness gate doc
This sentence has a grammatical mistake.
1 parent be812c3 commit 0202264

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/deploy/pod_readiness_gate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The pod readiness gate is needed under certain circumstances to achieve full zer
99

1010
* Low number of replicas in a deployment
1111
* Start a rolling update of the deployment
12-
* Rollout of new pods takes less time than it takes the AWS Load Balancer controller to register the new pods and for their health state turn »Healthy« in the target group
12+
* Rollout of new pods takes less time than it takes the AWS Load Balancer controller to register the new pods and for their health state to become »Healthy« in the target group
1313
* At some point during this rolling update, the target group might only have registered targets that are in »Initial« or »Draining« state; this results in service outage
1414

1515
In order to avoid this situation, the AWS Load Balancer controller can set the readiness condition on the pods that constitute your ingress or service backend. The condition status on a pod will be set to `True` only when the corresponding target in the ALB/NLB target group shows a health state of »Healthy«.

0 commit comments

Comments
 (0)