chore: Some minor fixes

Author: rhuss

advanced/ImageBuilder/knative/README.adoc

@@ -116,7 +116,7 @@ kubectl logs random-generator-with-template-pod-0ae221 -c build-step-image-build
 
 === Deploy application
 
-When you have build the random-generatot with one of the methods above, you can deploy it easily.
+When you have build the random-generator with one of the methods above, you can deploy it easily.
 Unfortunately, for picking up images, Kubernetes (or at least Minikube) doesn't support service DNS lookups in the `image:` field of a container specification.
 
 So we need to insert the IP adress directly which you can do while deploying, like in:

behavorial/DaemonService/daemonset.yml

@@ -13,9 +13,6 @@ spec:
       labels:
         app: random-refresher
     spec:
-      # Only use nodes with the label 'feature=hw-rng' enabled
-      nodeSelector:
-        feature: hw-rng
       # Also run on the the master even it's tainted
       tolerations:
       - key: node-role.kubernetes.io/master
@@ -28,7 +25,11 @@ spec:
         command:
         - sh
         - -c
-        - "while true; do java -cp / RandomRunner /host_dev/random 100000; sleep 30; done"
+        - >-
+          while true; do
+            java -cp / RandomRunner /host_dev/random 100000;
+            sleep 30;
+          done
         # Mount host's /dev directory
         volumeMounts:
         - mountPath: /host_dev

configuration/ConfigurationResource/pod.yml

@@ -30,8 +30,13 @@ spec:
     volumeMounts:
     - name: config-volume
       mountPath: /config
+    - name: secret-volume
+      mountPath: /secret
   volumes:
-  # Volume is mounted directly from a config map
+  - name: secret-volume
+    secret:
+      secretName: my-secret
   - name: config-volume
     configMap:
       name: random-generator-config
+  # Volume is mounted directly from a config map