Difference between revisions of "Kubernetes restartPolicy"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* <code>[[PodStatus]]: PodScheduled, ContainersReady, Initialized, Ready</code> | * <code>[[PodStatus]]: PodScheduled, ContainersReady, Initialized, Ready</code> | ||
| + | |||
| + | [[kubectl get deployments -o json -A]] | grep restartPolicy | ||
== Related == | == Related == | ||
Revision as of 16:54, 25 July 2022
Always, OnFailure, and Never.
PodStatus: PodScheduled, ContainersReady, Initialized, Ready
kubectl get deployments -o json -A | grep restartPolicy
Related
See also
- Kubernetes: distributions, tools, CKA, CKS, Kubernetes interfaces: CSI, CNI, installation, workloads, networking,
kubeadm,Kubernetes API, Kubernetes API Server,kubectl, kubeadm, kubelet, kube-proxy, Cloud services: EKS, GKE, TKE, DKS, Helm, Kubernetes RBAC, Kubernetes deployments, Minikube, Rancher, OpenShift, Charmed Kubernetes, Ingress, Kubernetes scheduler, Kubernetes Finalizers, logging, Kubernetes operator, Orka,kind:, Kubernetes namespaces, Kubernetes dashboard, Kubernetes Metrics Server, Field Selectors, CoreDNS, CRI, Kubernetes Topology Manager, Kubernetes governance: (SIG, KEP), Kustomize, controllers,ReadinessProbe, LivenessProbe, KOPS, K9s, Kui, k3s, ImagePullBackOff, PDB, EndPoints, Kots, metadata, Karpenter, Replicated.com, Kubernetes Authenticating, Kubernetes timeline, Changelog/Versions, service accounts, Kubernetes Pod Lifecycle, Kubernetes Conformance Certified, Kubernetes backup, Kubernetes Pod Security Admission, tEKS, Kubernetes events, Kubernetes ports, Kubernetes policies, Connect, addons, DoKC, Kubernetes control plane, Kubernetes Federation, Kubernetes info, Kubetest2, Sidecar (Kubernetes)
Advertising:
