OpenShift Deployment Operations: Difference between revisions
Jump to navigation
Jump to search
Line 26: | Line 26: | ||
oc get pods | oc get pods | ||
NAME | NAME READY STATUS RESTARTS AGE | ||
... | ... | ||
<''dc-name''>-1-deploy 1/1 Running 0 7m | <''dc-name''>-1-deploy 1/1 Running 0 7m |
Revision as of 00:08, 25 November 2017
External
Internal
Overview
View Deployment Controllers for Project
oc get dc
View the Latest Deployment for a Deployment Controller
oc deploy <deployment-controller-name>
For each on-going deployment, there is a deployment pod, whose name can be inferred from the list of pods for the project:
oc get pods
The log of the deployment can be obtained from the deployment pod:
oc get pods NAME READY STATUS RESTARTS AGE ... <dc-name>-1-deploy 1/1 Running 0 7m
View Deployments for Project
oc get deploy
The deployments returned by this list are backed by deployment pods, which can be retrieved with
oc get pods
View Deployment Events
oc describe dc <deployment-configuration-name>
View Deployment Logs
View deployment logs for a deployment:
oc logs -f deploy/<deploy-object-name>
Starting a Deployment
oc rollout latest dc/<deploymentconfig-name>
This will start the number of replicas specified in ?
oc scale dc logging-es-3fs5ghyo --replicas=1
scaling the pod instead of the deploymentconfig may modify the deployment config. Verify
Assigning Pods to Specific Nodes
Assigning a Pod to Nodes that Match a Node Selector
Edit the DeploymentConfig that defines the pod:
oc edit dc/<pod-name>
Inject the node selector specification under
spec: ... template: ... spec: ... nodeSelector: keyA: valueA
Restart the corresponding pod, by simply deleting it.
For more details on concepts related to pod placement, see:
Turn Off Auto-Deployment After Build
oc set triggers dc/<deployment-config-name> --remove-all