Skip to content

Commit ce934f6

Browse files
authored
State supported target-type more clearly in pod readiness gate documentation (#1815)
Closes #1814.
1 parent 9c719f7 commit ce934f6

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/deploy/pod_readiness_gate.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22

33
AWS Load Balancer controller supports [»Pod readiness gates«](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-readiness-gate) to indicate that pod is registered to the ALB/NLB and healthy to receive traffic.
44
The controller automatically injects the necessary readiness gate configuration to the pod spec via mutating webhook during pod creation.
5-
For readiness gate configuration to be injected to the pod spec, you need to apply the label `elbv2.k8s.aws/pod-readiness-gate-inject: enabled` to the pod namespace.
5+
6+
For readiness gate configuration to be injected to the pod spec, you need to apply the label `elbv2.k8s.aws/pod-readiness-gate-inject: enabled` to the pod namespace. However, note that this only works with `target-type: ip`, since when using `target-type: instance`, it's the node used as backend, the ALB itself is not aware of pod/podReadiness in such case.
67

78
The pod readiness gate is needed under certain circumstances to achieve full zero downtime rolling deployments. Consider the following example:
89

0 commit comments

Comments
 (0)