OpenShift Pod Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 52: Line 52:
Only pods backed by [[OpenShift Concepts#Replication_Controller|replication controllers]] can be evacuated. The [[OpenShift_Concepts#Bare_Pod|"bare" pods]] cannot be evacuated.
Only pods backed by [[OpenShift Concepts#Replication_Controller|replication controllers]] can be evacuated. The [[OpenShift_Concepts#Bare_Pod|"bare" pods]] cannot be evacuated.


Mark the node as unschedulable.
Mark the node as unschedulable:
 
oadm manage-node <''node-name''> --evacuate --dry-run [--pod-selector=<pod_selector>]


=Scaling Down and Up the Number of Replicas associated with a DeploymentConfig=
=Scaling Down and Up the Number of Replicas associated with a DeploymentConfig=


{{Internal|OpenShift_Application_Operations#Scaling_Up_and_Down_the_Number_of_Replicas_associated_with_a_DeploymentConfig|Application Operations - Scaling Up and Down the Number of Replicas associated with a DeploymentConfig}}
{{Internal|OpenShift_Application_Operations#Scaling_Up_and_Down_the_Number_of_Replicas_associated_with_a_DeploymentConfig|Application Operations - Scaling Up and Down the Number of Replicas associated with a DeploymentConfig}}

Revision as of 04:50, 22 November 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

The most complete information set is generated by "oc get -o yaml pod ..." and "oc describe pod ...":

oc [-n <project-name>] [[oc get#pods|get pods]
oc [-n <project-name>] -o yaml get pod] <pod-name>
oc [-n <project-name>] describe pod <pod-name>
oc [-n <project-name>] describe pod/<pod-name>
oc [-n <project-name>] edit pod/<pod-name>

Monitor Pod's Logs

oc logs -f <pod-name>

Execute Commands in Containers

oc rsh <pod-id> <command>

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.

Evacuate Pods from Node

https://docs.openshift.com/container-platform/latest/admin_guide/manage_nodes.html#evacuating-pods-on-nodes

Only pods backed by replication controllers can be evacuated. The "bare" pods cannot be evacuated.

Mark the node as unschedulable:

oadm manage-node <node-name> --evacuate --dry-run [--pod-selector=<pod_selector>]

Scaling Down and Up the Number of Replicas associated with a DeploymentConfig

Application Operations - Scaling Up and Down the Number of Replicas associated with a DeploymentConfig