chore: Minor tuning

Author: rhuss

advanced/Controller/README.adoc

@@ -52,7 +52,13 @@ Now you have a nice little Controller which watches on `ConfigMap` and restart `
 To try it out, we are reusing the super simple web application which just exposes an environment variable as content.
 This link:../images/mini-http-server.dockerfile[image] uses `nc` to deliver the content and can be found on Docker Hub as https://cloud.docker.com/u/k8spatterns/repository/docker/k8spatterns/mini-http-server[k8spatterns/mini-http-server].
 
-Before we deploy this app, we should tail on the log of our controller (e.g. `kubectl logs -f config-watcher-controller-....`) to see the events received by the controller as they come in.
+Before we deploy this app, we should tail on the log of our controller (e.g. `kubectl logs -f config-watcher-controller-....`) to see the events received by the controller as they come in, e.g. with
+
+[source,bash]
+----
+controller_pod=$(kubectl get pod -o name | grep config-watcher-controller | sed -e "s/^pods\///")
+kubectl logs -f $controller_pod config-watcher
+----
 
 Then create the web application itself:
 
@@ -65,6 +71,9 @@ kubectl create -f web-app.yml
 If you look into this descriptor, you will find a `Deployment` using our dumb HTTP server which references the content environment variable via a `ConfigMap`.
 The `ConfigMap` itself is annotated with a pod selector `k8spatterns.io/podDeleteSelector: "app=webapp"` which directly select the webapp `Pod`.
 
+This resource file also includes the definition of a Service and an Ingress object so that we can access the server from the outside.
+
+
 You can access our web app directly
 
 [source,bash]

advanced/Operator/README.adoc

@@ -25,6 +25,11 @@ As a first step, we have to install the CRD along with a role to allow to modify
 ----
 # Register ConfigWatcher CRD
 kubectl create -f config-watcher-crd.yml
+
+# Verify that the CRD is registered
+$ kubectl get crd
+NAME                            CREATED AT
+configwatchers.k8spatterns.io   2018-12-28T17:19:28Z
 ----
 
 The operator script itself is stored in a `ConfigMap`:
@@ -82,6 +87,11 @@ We have to first install a concreate custom resource of kind `ConfigWatcher` to
 ----
 # Install a ConfigWatcher custom resource
 kubectl create -f config-watcher-sample.yml
+
+# Check that the resource has been created
+kubectl get configwatchers
+NAME                      AGE
+webapp-config-watcher     1m
 ----
 
 After this connection between `ConfigMap` and `Pods` has been configured, change the content of `ConfigMap` and watch the operator log:
@@ -96,6 +106,6 @@ and then finally call the URL again to check that the content has been updated
 
 [source, bash]
 ----
-# Access webapp via the included Ingress obect
+# Access webapp via the included Ingress object
 curl -sk https://webapp.$(minikube ip).nip.io
 ----