Skip to content

Commit 0f0ccd1

Browse files
authored
Merge pull request kubernetes#6725 from fatsheep9146/fix-links
Fix broken links
2 parents 9f830f8 + 2345c7b commit 0f0ccd1

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/concepts/workloads/pods/pod-lifecycle.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This page describes the lifecycle of a Pod.
1717
## Pod phase
1818

1919
A Pod's `status` field is a
20-
[PodStatus](/docs/resources-reference/{{page.version}}/#podstatus-v1-core)
20+
[PodStatus](/docs/api-reference/{{page.version}}/#podstatus-v1-core)
2121
object, which has a `phase` field.
2222

2323
The phase of a Pod is a simple, high-level summary of where the Pod is in its
@@ -52,30 +52,30 @@ Here are the possible values for `phase`:
5252
## Pod conditions
5353

5454
A Pod has a PodStatus, which has an array of
55-
[PodConditions](/docs/resources-reference/{{page.version}}/#podcondition-v1-core). Each element
55+
[PodConditions](/docs/api-reference/{{page.version}}/#podcondition-v1-core). Each element
5656
of the PodCondition array has a `type` field and a `status` field. The `type`
5757
field is a string, with possible values PodScheduled, Ready, Initialized, and
5858
Unschedulable. The `status` field is a string, with possible values True, False,
5959
and Unknown.
6060

6161
## Container probes
6262

63-
A [Probe](/docs/resources-reference/{{page.version}}/#probe-v1-core) is a diagnostic
63+
A [Probe](/docs/api-reference/{{page.version}}/#probe-v1-core) is a diagnostic
6464
performed periodically by the [kubelet](/docs/admin/kubelet/)
6565
on a Container. To perform a diagnostic,
6666
the kubelet calls a
6767
[Handler](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#Handler) implemented by
6868
the Container. There are three types of handlers:
6969

70-
* [ExecAction](/docs/resources-reference/{{page.version}}/#execaction-v1-core):
70+
* [ExecAction](/docs/api-reference/{{page.version}}/#execaction-v1-core):
7171
Executes a specified command inside the Container. The diagnostic
7272
is considered successful if the command exits with a status code of 0.
7373

74-
* [TCPSocketAction](/docs/resources-reference/{{page.version}}/#tcpsocketaction-v1-core):
74+
* [TCPSocketAction](/docs/api-reference/{{page.version}}/#tcpsocketaction-v1-core):
7575
Performs a TCP check against the Container's IP address on
7676
a specified port. The diagnostic is considered successful if the port is open.
7777

78-
* [HTTPGetAction](/docs/resources-reference/{{page.version}}/#httpgetaction-v1-core):
78+
* [HTTPGetAction](/docs/api-reference/{{page.version}}/#httpgetaction-v1-core):
7979
Performs an HTTP Get request against the Container's IP
8080
address on a specified port and path. The diagnostic is considered successful
8181
if the response has a status code greater than or equal to 200 and less than 400.
@@ -129,11 +129,11 @@ to stop.
129129
## Pod and Container status
130130

131131
For detailed information about Pod Container status, see
132-
[PodStatus](/docs/resources-reference/{{page.version}}/#podstatus-v1-core)
132+
[PodStatus](/docs/api-reference/{{page.version}}/#podstatus-v1-core)
133133
and
134-
[ContainerStatus](/docs/resources-reference/{{page.version}}/#containerstatus-v1-core).
134+
[ContainerStatus](/docs/api-reference/{{page.version}}/#containerstatus-v1-core).
135135
Note that the information reported as Pod status depends on the current
136-
[ContainerState](/docs/resources-reference/{{page.version}}/#containerstatus-v1-core).
136+
[ContainerState](/docs/api-reference/{{page.version}}/#containerstatus-v1-core).
137137

138138
## Restart policy
139139

0 commit comments

Comments
 (0)