anchor.diff:  	$ kubectl delete -f templates/deployment.yaml
   	deployment "nginx-deployment" deleted
   
  -== Replica Sets
  +== 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 ReplicaSet
  +=== Create a Replica Set
   
   The folowing is an example ReplicaSet with an NGINX base image. Let's begin with the template:
   
  
positive.code: 
  The output shows that the job was successfully executed.
  
  The list of completed pods can be seen using the following command:
  
  	$ kubectl get pods --show-all
  	NAME         READY     STATUS      RESTARTS   AGE
  
negative.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 the cluster version >= 1.8. You should switch to `batch/v1beta1`. This version is enabled by default in the API server.
  
  === Create Cron Job
  
  