anchor.diff:  	$ kubectl delete rs/nginx-replicaset
   	replicaset "nginx-replicaset" deleted
   
  -== Services
  +== Service
   
   A pod is ephemeral. Each pod is assigned a unique IP address. If a pod that belongs to a replication controller dies, then it is recreated and may be given a different IP address. Further, aAdditional pods may be created using Deployment or Replica Set. This makes it difficult for an application server, such as WildFly, to access a database, such as MySQL, using its IP address.
   
  
positive.code: 
  For Kubernetes cluster versions < 1.8, Cron Job is created with API version `batch/v2alpha1`. This version needs to be explicitly enabled in the Kubernetes cluster as explained in link:cluster-install#turn-on-an-api-version-for-your cluster[Turn on an API version for your cluster].
  
  `batch/v2alpha1` API version for Cron Job is deprecated for cluster version >= 1.8. You should switch to `batch/v1beta1`. This version is enabled by default in the API server.
  
  === Create Cron Job
  
  
negative.code: 	$ kubectl delete -f templates/deployment.yaml
  	deployment "nginx-deployment" deleted
  
  == Replica Set
  
  A RepllicaSet specifies a number of pod replicas that can be run at any given time. The Deployment manages the ReplicaSets and provides updates to those pods. ReplicaSets can be used in lieu of Deployments if you require custom orchestration or do not need updates.
  
  For replica set, matching of pods is done according to a set of values. The supported operators are `in`, `notin` and `exists` (only for the key). For example, replication controller can select pods such as "`environment = dev`". Replica set can select pods such as "`environment in ["dev", "test"]`".
  
  === Create a Replica Set
  
  The folowing is an example ReplicaSet with an NGINX base image. Let's begin with the template:
  
  