OpenShift Pod Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 39: Line 39:
=Scaling Down and Up the Number of Replicas associated with a DeploymentConfig=
=Scaling Down and Up the Number of Replicas associated with a DeploymentConfig=


This procedure can be applied after a configuration change, such as a modification in the [[OpenShift Concepts#ConfigMap|ConfigMap]].
{{InternalOpenShift_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}}
 
Identify the name of the deployment config:
 
oc get dc -o name --selector=....
 
or
 
oc get dc
 
Then set the number of replicas to 0:
 
oc scale deploymentconfig/<''deploymentconfig-name''> --replicas=0
 
After all pods associated with deployment configuration have been stopped, scale it back up again.
 
oc scale deploymentconfig/<''deploymentconfig-name''> --replicas=1

Revision as of 17:18, 21 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>

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 and Up the Number of Replicas associated with a DeploymentConfig

Template:InternalOpenShift Application Operations