anchor.diff:  [id="nodes-pods-using-example_{context}"]
   = Example pod configurations
   
  -{product-title} leverages the Kubernetes concept of a _pod_, which is one or more containers deployed
  -together on one host, and the smallest compute unit that can be defined,
  -deployed, and managed.
  +{product-title} leverages the Kubernetes concept of a _pod_, which is one or more containers deployed together on one host, and the smallest compute unit that can be defined, deployed, and managed.
   
  -The following is an example definition of a pod that provides a long-running
  -service, which is actually a part of the {product-title} infrastructure: the
  -integrated container image registry. It demonstrates many features of pods, most of
  -which are discussed in other topics and thus only briefly mentioned here:
  +The following is an example definition of a pod from a Rails application. It demonstrates many features of pods, most of which are discussed in other topics and thus only briefly mentioned here:
   
   [id="example-pod-definition_{context}"]
   .`Pod` object definition (YAML)
  
positive.code:   uid: 5cc30063-0265780783bc
    resourceVersion: '165032'
    creationTimestamp: '2019-02-13T20:31:37Z'
    labels:                  <1>
      app: hello-openshift
    annotations:
      openshift.io/scc: anyuid
  spec:
    restartPolicy: Always      <2>
    serviceAccountName: default
    imagePullSecrets:
      - name: default-dockercfg-5zrhb
  
negative.code:         - containerPort: 8080
            protocol: TCP
        imagePullPolicy: Always
        volumeMounts: <5>
          - name: default-token-wbqsl
            readOnly: true
            mountPath: /var/run/secrets/kubernetes.io/serviceaccount
        terminationMessagePolicy: File
        image: registry.redhat.io/openshift4/ose-ogging-eventrouter:v4.3 <6>
    serviceAccount: default <7>
    volumes: <8> 
      - name: default-token-wbqsl
        secret:
          secretName: default-token-wbqsl
  