anchor.diff:  
   As a very last step we can delete the original `kube-dns` deployment: `kubectl delete deployment kube-dns -n kube-system`
   
  -This will delete the pod and only our coredns implementation will still be available.
  +This will delete the pod, and the CoreDNS implementation will still be available.
   
  
positive.code: 
  As expected, the nameserver IP corresponds to the IP of the `kube-dns` service. Additionally, the search domains also reflect the expected kubernetes schema (get more https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/[here]).
  
  == Deploying coredns
  
  The `coredns` deployment relies on information which is specific to you cluster: CIDR of kubernetes services and cluster domain. For minikube, you can deploy `coredns` from a pre-generated yaml: `kubectl create -f coredns-minikube.yaml`
  
  Wait until the `coredns` pod is running:
  ```
  kubectl get po -l k8s-app=coredns -n kube-system
  NAME                       READY     STATUS    RESTARTS   AGE
  coredns-3986650266-gw79f   1/1       Running   0          17s
  ```
  
  == Switching to coredns
  
  The only thing left is updating the `kube-dns` service to use our coredns pod: `kubectl apply -f coredns-service.yaml`
  
  When you describe the `kube-dns` service now, it should look something like this:
  ```
  kubectl describe svc kube-dns -n kube-system
  Name:			kube-dns
  
negative.code: Events:			<none>
  ```
  
  If all went correct, the IP of our CoreDNS pod should match the endpoint IPs in the `kube-dns` service:
  
  	kubectl get po -l k8s-app=coredns -n kube-system -o wide
  	NAME                       READY     STATUS    RESTARTS   AGE       IP            NODE
  	coredns-3986650266-gw79f   1/1       Running   0          20m       172.17.0.10   minikube
  
  Awesome, this fits nicely!
  
  