8459ch06.fm Draft Document for Review December 11, 2019 1:55 pm If the details provided by the  oc get  command are not sufficient, additional information about  the resource can be retrieved by using the  oc describe RESOURCE_TYPE  RESOURCE_NAME  command. Unlike the  oc get  command, there is no way to iterate  through all of the different resources by type. Although most major resources can be  described, this functionality is not available across all resources. To display detailed  information about a Pod resource use the following command: Use the  oc export RESOURCE_TYPE RESOURCE_NAME [-o OUTPUT_FORMAT] command to export a definition of a resource. Typical use cases include creating a backup, or  to aid in modifying a definition. By default, the export command prints out the object  representation in YAML format, but this can be changed by providing the  -o  option. Use the  oc delete RESOURCE_TYPE RESOURCE_NAME  command to remove a resource  from the OpenShift cluster.  Use the  oc create  command to create resources from a resource definition. Typically, this is  paired with the  oc export  command for editing definitions. oc describe pod docker-registry-3-4flql Name: docker-registry-3-4flql Namespace: default Priority: 0 PriorityClassName: <none> Node: mstnode02.domain.example.com/192.168.11.203 Start Time: Thu, 07 Nov 2019 16:09:12 +0000 Labels: deployment=docker-registry-3 deploymentconfig=docker-registry docker-registry=default Annotations: openshift.io/deployment-config.latest-version=3 openshift.io/deployment-config.name=docker-registry openshift.io/deployment.name=docker-registry-3 openshift.io/scc=restricted Status: Running IP: 10.130.0.48 ... Output truncated ... Volumes: registry-storage: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the s ame namespace) ClaimName: registry-pvc ReadOnly: false registry-token-zg2tb: Type: Secret (a volume populated by a Secret) SecretName: registry-token-zg2tb Optional: false QoS Class: Burstable Node-Selectors: node-role.kubernetes.io/infra=true Tolerations: node.kubernetes.io/memory-pressure:NoSchedule Events: <none> Note:  A fundamental understanding of the OpenShift architecture is needed because  deleting managed resources such as Pods results in newer instances of those resources  being automatically recreated. The  oc new-app  command can create application Pods to run on OpenShift in many different  ways. It can create Pods from existing docker images, from Dockerfiles, and from raw source  code using the Source-to-Image (S2I) process. The command can create a service, a  deployment configuration, and a build configuration if source code is used. Use the  oc exec POD_NAME COMMAND  command to execute commands against a Pod: 144  Red Hat OpenShift and IBM Cloud Paks on IBM Power Systems: Volume 1