text: **Services**
  Kubernetes Service is one more REST object and is similar to a pod. However, this service is 
  designed as an abstraction for logical set of pods and associated policy to access those sets. 
  This abstraction enables cloud-based applications to be decoupled from its endpoints. A 
  Service definition is posted to API server to create a Service instance with or without Selector 
  definition. Cloud native applications take advantage of the API server to query and discover 
  Service endpoints, along with notification for changes in pods that are associated with a 
  service. 
  
  **Service with selector**
  Service with selector includes the following features: 
  
  (cid:2) An object is created with cluster IP, which is assigned by Kubernetes to new a Service 
  object 
  
  (cid:2) Automatically creates endpoints 
  
  (cid:2) Controller scans and find this service with the reference of Service selector 
  
  **Service without selector**
  Service without selector includes the following features: 
  
  (cid:2) Maps with objects from external clusters 
  
  (cid:2) Maps with objects from different namespace 
  
  (cid:2) During phased migration, section of objects from be run as a backend process 
  
  (cid:2) Endpoint objects are not created automatically (requires manual mapping of service with 
  IP and ports) 
  
  **Storage volume**
  Kubernetes volume is an abstraction to address two important aspects, such as data 
  persistency and sharing. Data persistency helps to retain the most updated data set after a 
  container is stopped or crashed. Data sharing can be an essential requirement if multiple 
  containers are hosted in a pod. 