OpenShift Pod Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 16: | Line 16: | ||
oc [-n ''<project-name>''] [[Oc_describe#pod|describe]] pod ''<pod-name>'' | oc [-n ''<project-name>''] [[Oc_describe#pod|describe]] pod ''<pod-name>'' | ||
oc [-n ''<project-name>''] [[Oc_describe#pod|describe]] pod/''<pod-name>'' | oc [-n ''<project-name>''] [[Oc_describe#pod|describe]] pod/''<pod-name>'' | ||
=Stopping Pods= | |||
A pod can be stopped by deleting its associated "pod" object: | |||
oc delete pod/logging-fluentd-3kz30 | |||
The controller (either [[OpenShift_Concepts#Replication_Controller|replication]] or [[OpenShift_Concepts#DaemonSet|DamonSet]]) will detect that the pod is missing and it will start a new one. | |||
Revision as of 00:49, 31 July 2017
External
Internal
List Pods on Nodes
oadm manage-node <node-name> --list-pods
Pod Status
oc [-n <project-name>] get pods oc [-n <project-name>] describe pod <pod-name> oc [-n <project-name>] describe pod/<pod-name>
Stopping Pods
A pod can be stopped by deleting its associated "pod" object:
oc delete pod/logging-fluentd-3kz30
The controller (either replication or DamonSet) will detect that the pod is missing and it will start a new one.