You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* RestartPolicy defines the restart behavior of individual containers in a pod. This field may only be
408
+
* set for init containers, and the only allowed value is "Always". For non-init containers or when this
409
+
* field is not specified, the restart behavior is defined by the Pod's restart policy and the container
410
+
* type. Setting the RestartPolicy as "Always" for the init container will have the following effect: this
411
+
* init container will be continually restarted on exit until all regular containers have terminated.
412
+
* Once all regular containers have completed, all init containers with restartPolicy "Always" will be
413
+
* shut down. This lifecycle differs from normal init containers and is often referred to as a "sidecar"
414
+
* container. Although this init container still starts in the init container sequence, it does not wait for
415
+
* the container to complete before proceeding to the next init container. Instead, the next init
416
+
* container starts immediately after this init container is started, or after any startupProbe has
417
+
* successfully completed.
418
+
*/
419
+
restartPolicy?: string;
420
+
406
421
// @todo:
407
422
// securityContext SecurityContext SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
408
423
// startupProbe Probe StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
@@ -312,7 +325,7 @@ class Pod extends KubeObject<KubePod> {
312
325
returnfalse;
313
326
}
314
327
315
-
// Implementation based on: https://github.com/kubernetes/kubernetes/blob/7b6293b6b6a5662fc37f440e839cf5da8b96e935/pkg/printers/internalversion/printers.go#L759
328
+
// Implementation based on: https://github.com/kubernetes/kubernetes/blob/67216cfdd980cdd0234866d66a9ffe2ba3d8fcc4/pkg/printers/internalversion/printers.go#L891
316
329
getDetailedStatus(): PodDetailedStatus{
317
330
// We cache this data to avoid going through all this logic when nothing has changed
318
331
if(
@@ -331,22 +344,58 @@ class Pod extends KubeObject<KubePod> {
0 commit comments