anchor.diff:    key: QVFBOFF2SlZheUJQRVJBQWgvS2cwT1laQUhPQno3akZwekxxdGc9PQ== <1>
   
   ----
  -<1> this base64 key is generated on one of the ceph MON nodes using the following command:
  -  `ceph auth get-key client.admin | base64`
  -and then copying the output and pasting it as the secret key's value.
  +<1> This base64 key is generated on one of the Ceph MON nodes using the `ceph auth get-key client.admin | base64` command, then copying the output and pasting it as the secret key's value.
   ====
   
   Save the secret definition to a file, for example *_ceph-secret.yaml_*,
  
positive.code: ...
  ----
  <1> `*securityContext*` must be defined at the pod level, not under a specific container.
  <2> all containers in the pod will have the same fsGroup id.
  ====
  
  
negative.code: ceph-pod1   1/1       Running   0          2m
                        <1>
  ----
  <1> After a minute or so, the pod will be in the *Running* state.
  ====
  
  [[using-ceph-rbd-defining-group-and-owner-ids-optional]]
  == Defining Group and Owner IDs (Optional)
  When using block storage, such as Ceph RBD, the physical block storage is
  *managed* by the pod. The group ID defined in the pod becomes the group ID of
  *both* the Ceph RBD mount inside the container, and the group ID of the actual
  storage itself. Thus, it is usually unnecessary to define a group ID in the pod
  specifiation. However, if a group ID is desired, it can be defined using
  `*fsGroup*`, as shown in the following pod definition fragment:
  
  .Group ID Pod Definition
  ====
  