148 Red Hat OpenShift and IBM Cloud Paks on IBM Power Systems: Volume 1
If the RESOURCE_NAME parameter is omitted, all resources of the specified RESOURCE_TYPE are 
summarized, as shown in Example 6-12.
Example 6-12   oc get pod
# oc get pod
NAME                      READY     STATUS    RESTARTS   AGE
docker-registry-3-4flql   1/1       Running   2          1d
router-2-4gnmj            1/1       Running   3          1d
router-2-cp5sf            1/1       Running   3          1d
router-2-slkjf            1/1       Running   3          1d
Use the oc types command for a quick refresher on the concepts of the available 
RESOURCE_TYPES, as shown in Example 6-13.
Example 6-13   oc types
# oc types
Command "types" is deprecated, refer to official documentation instead
Concepts and Types 
Kubernetes and OpenShift help developers and operators build, test, and deploy applications 
in a containerized cloud
environment. Applications may be composed of all of the components below, although most 
developers will be concerned
with Services, Deployments, and Builds for delivering changes. 
Concepts: 
* Containers:
    A definition of how to run one or more processes inside of a portable Linux
    environment. Containers are started from an Image and are usually isolated
    from other containers on the same machine.
    
* Image:
    A layered Linux filesystem that contains application code, dependencies,
    and any supporting operating system libraries. An image is identified by
    a name that can be local to the current cluster or point to a remote Docker
    registry (a storage server for images).
    
* Pods [pod]:
    A set of one or more containers that are deployed onto a Node together and
    share a unique IP and Volumes (persistent storage). Pods also define the
    security and runtime policy for each container.
    
* Labels:
    Labels are key value pairs that can be assigned to any resource in the
    system for grouping and selection. Many resources use labels to identify
    sets of other resources.
    
* Volumes:
    Containers are not persistent by default - on restart their contents are
    cleared. Volumes are mounted filesystems available to Pods and their
    containers which may be backed by a number of host-local or network
    attached storage endpoints. The simplest volume type is EmptyDir, which
    is a temporary directory on a single machine. Administrators may also
    allow you to request a Persistent Volume that is automatically attached
    to your pods.
    
* Nodes [node]: