@@ -17,7 +17,7 @@ This page describes the lifecycle of a Pod.
17
17
## Pod phase
18
18
19
19
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 )
21
21
object, which has a ` phase ` field.
22
22
23
23
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`:
52
52
## Pod conditions
53
53
54
54
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
56
56
of the PodCondition array has a ` type ` field and a ` status ` field. The ` type `
57
57
field is a string, with possible values PodScheduled, Ready, Initialized, and
58
58
Unschedulable. The ` status ` field is a string, with possible values True, False,
59
59
and Unknown.
60
60
61
61
## Container probes
62
62
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
64
64
performed periodically by the [ kubelet] ( /docs/admin/kubelet/ )
65
65
on a Container. To perform a diagnostic,
66
66
the kubelet calls a
67
67
[ Handler] ( https://godoc.org/k8s.io/kubernetes/pkg/api/v1#Handler ) implemented by
68
68
the Container. There are three types of handlers:
69
69
70
- * [ ExecAction] ( /docs/resources -reference/{{page.version}}/#execaction-v1-core ) :
70
+ * [ ExecAction] ( /docs/api -reference/{{page.version}}/#execaction-v1-core ) :
71
71
Executes a specified command inside the Container. The diagnostic
72
72
is considered successful if the command exits with a status code of 0.
73
73
74
- * [ TCPSocketAction] ( /docs/resources -reference/{{page.version}}/#tcpsocketaction-v1-core ) :
74
+ * [ TCPSocketAction] ( /docs/api -reference/{{page.version}}/#tcpsocketaction-v1-core ) :
75
75
Performs a TCP check against the Container's IP address on
76
76
a specified port. The diagnostic is considered successful if the port is open.
77
77
78
- * [ HTTPGetAction] ( /docs/resources -reference/{{page.version}}/#httpgetaction-v1-core ) :
78
+ * [ HTTPGetAction] ( /docs/api -reference/{{page.version}}/#httpgetaction-v1-core ) :
79
79
Performs an HTTP Get request against the Container's IP
80
80
address on a specified port and path. The diagnostic is considered successful
81
81
if the response has a status code greater than or equal to 200 and less than 400.
@@ -129,11 +129,11 @@ to stop.
129
129
## Pod and Container status
130
130
131
131
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 )
133
133
and
134
- [ ContainerStatus] ( /docs/resources -reference/{{page.version}}/#containerstatus-v1-core ) .
134
+ [ ContainerStatus] ( /docs/api -reference/{{page.version}}/#containerstatus-v1-core ) .
135
135
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 ) .
137
137
138
138
## Restart policy
139
139
0 commit comments