OpenShift Pod Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
=Scaling Down the Number of Replicas associated with a DeploymentConfig= | =Scaling Down the Number of Replicas associated with a DeploymentConfig= | ||
Identify the deployment config: | Identify the name of the deployment config: | ||
oc get dc -o name --selector=.... | oc get dc -o name --selector=.... | ||
Revision as of 01:52, 13 October 2017
External
Internal
List Pods for a Project
oc get projects oc get -n <project-name> pods
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> oc [-n <project-name>] edit pod/<pod-name>
Update a Pod Defintion
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.
Scaling Down the Number of Replicas associated with a DeploymentConfig
Identify the name of the deployment config:
oc get dc -o name --selector=....
or
oc get dc