Skip to content

Commit f10369c

Browse files
authored
changes done as per reviews
Signed-off-by: GitHub <[email protected]>
1 parent 02aa31c commit f10369c

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -488,9 +488,9 @@ startupProbe:
488488
```
489489

490490
{{< note >}}
491-
When the kubelet probes a Pod using HTTP, the default behavior is only to follows redirects if the redirect
492-
is to the same host. If the kubelet receives 11 or more redirects during probing, the probe is considered a
493-
warning and a related Event is created:
491+
When the kubelet probes a Pod using HTTP, it only follows redirects if the redirect
492+
is to the same host. If the kubelet receives 11 or more redirects during probing, the probe is considered successful
493+
and a related Event is created:
494494

495495
```none
496496
Events:
@@ -504,8 +504,7 @@ Events:
504504
Warning ProbeWarning 4m11s (x1197 over 24m) kubelet Readiness probe warning: Probe terminated redirects
505505
```
506506

507-
If the kubelet receives a redirect where the hostname is different from the request, the outcome of the probe
508-
is a warning and the kubelet creates an event to report this.
507+
If the kubelet receives a redirect where the hostname is different from the request, the outcome of the probe is treated as successful and kubelet creates an event to report the redirect failure.
509508
{{< /note >}}
510509

511510
### TCP probes

0 commit comments

Comments
 (0)