text: (cid:2) persistentVolumeClaim 
  (cid:2) projected 
  (cid:2) portworxVolume 
  (cid:2) quobyte 
  (cid:2) rbd 
  (cid:2) scaleIO 
  (cid:2) secret 
  (cid:2) storageos 
  (cid:2) vsphereVolume 
  
  **NameSpace**
  Kubernetes NameSpace is set of virtual clusters that are backed by physical clusters. 
  NameSpace is intended to divide cluster between users to provide an isolated and secure 
  environment. NameSpaces are built with unique names. But the same name can be present 
  in different NameSpaces. Therefore, a Name is supposed to be unique in a NameSpaces, but 
  not so when it encounters NameSpaces. A NameSpace must not be nested. 
  
  **Controller**
  Controller is another Kubernetes abstraction that handles the availability of a pod. Therefore, 
  the most preferred practice is to use the Controller to manage pods. A Controller can create 
  and manage multiple pods for you. It also can handle replication and rollout and provide 
  self-healing capabilities at the cluster scope. For example, if a node fails, the Controller might 
  automatically replace the pod by scheduling an identical replacement on a different node. 
  
  **ReplicaSet**
  ReplicaSet is the process to maintain the configured availability level with a specified number 
  of identical pods in the Kubernetes Cluster. A ReplicaSet must be created with a selector and 
  the template to include specifications for pod instances to be created or deleted to meet the 
  needed availability level. This task is performed by ReplicationController. A ReplicaSet 
  identifies new pods to acquire by using its selector. 