Some fixes

Author: rhuss

advanced/ElasticScale/.gitignore

@@ -0,0 +1 @@
+autoscaler

advanced/ElasticScale/README.adoc

@@ -8,8 +8,9 @@ IMPORTANT: The instructions have not been written/finished, but you can already
 # Start Minikiube with 8GB of RAM
 minikube start --memory 4096
 
-# Enable metrics-server for measuring
+# Enable metrics-server and heapster for measuring
 minikube addons enable metrics-server
+minikube addons enable heapster
 
 # Create deployment for out random service
 kubectl create -f deployment.yml
@@ -18,10 +19,10 @@ kubectl create -f deployment.yml
 kubectl autoscale deployment random-generator --min=1 --max=10 --cpu-percent=50
 
 # Same for V2
-kubectl create -f deployment.yml
+kubectl create -f hpa.yml
 
 # Put some load on the system
-port=$(kubectl get svc random-generator-np -o jsonpath={.spec.ports[0].nodePort})
+port=$(kubectl get svc random-generator -o jsonpath={.spec.ports[0].nodePort})
 while true; do curl -s http://$(minikube ip):port?burn=10000 >/dev/null; done
 
 # In other terminal:

advanced/ElasticScale/hpa.yml

@@ -1,15 +1,10 @@
 apiVersion: autoscaling/v2beta2
 kind: HorizontalPodAutoscaler
 metadata:
-  creationTimestamp: "2019-02-09T17:18:38Z"
   name: random-generator
-  namespace: default
-  resourceVersion: "796"
-  selfLink: /apis/autoscaling/v2beta2/namespaces/default/horizontalpodautoscalers/random-generator
-  uid: bd57a211-2c8e-11e9-86e0-080027613e7d
 spec:
   scaleTargetRef:
-    apiVersion: extensions/v1beta1
+    apiVersion: apps/v1
     kind: Deployment
     name: random-generator
   maxReplicas: 20

advanced/ElasticScale/vpa.yml

@@ -1,10 +1,11 @@
-apiVersion: "autoscaling.k8s.io/v1beta1"
+apiVersion: "autoscaling.k8s.io/v1beta2"
 kind: VerticalPodAutoscaler
 metadata:
   name: random-generator
 spec:
   updatePolicy:
     updateMode: Recreate
-  selector:
-    matchLabels:
-      app: random-generator
+  targetRef:
+    apiVersion: "apps/v1"
+    kind: Deployment
+    name: random-generator

behavorial/BatchJob/README.adoc

@@ -14,6 +14,13 @@ To access the PersistentVolume used in this demo, let's mount a local directory
 minikube start --mount --mount-string="$(pwd)/logs:/example"
 ----
 
+Alternatively, you can mount the directory on the fly in the background
+
+[source,bash]
+----
+minikube mount $(pwd)/logs:/example
+----
+
 This makes this directory available within the Minikube VM at the path `/example`.
 
 Let's create now the PersistentVolume along with a PVC which can be mounted into our Job later:

behavorial/DaemonService/daemonset.yml

@@ -1,6 +1,6 @@
 # DaemonSet resource
 ---
-apiVersion: extensions/v1beta1
+apiVersion: apps/v1
 kind: DaemonSet
 metadata:
   name: random-refresher

behavorial/SingletonService/pdb.yml

@@ -9,5 +9,5 @@ spec:
     matchLabels:
       # Used for counting active Pods for which this PDB is used
       app: random-generator
-  # At least two need to be available all the time
+  # At least four need to be available all the time
   minAvailable: 4

behavorial/StatefulService/README.adoc

@@ -1,8 +1,6 @@
 == Stateful Service
 
-IMPORTANT: The instructions have not been written/finished, but the resource file has been verified. Instructions will be added soon.
-
-In this example we will examine how a _Statefule Service_ can implemented with the help of a StatefulSet resource.
+In this example we will examine how a _Stateful Service_ can implemented with the help of a StatefulSet resource.
 
 This example assumes a Kubernetes installation available.
 For the moment we are using Minikube as we need some support for PersistentVolumes.
@@ -15,6 +13,13 @@ To access the PersistentVolume used in this demo, let's mount a local directory
 minikube start --mount --mount-string="$(pwd)/logs:/tmp/example"
 ----
 
+Alternatively start the mount after your minikube is running
+[source, bash]
+----
+minikube mount $(pwd)/logs:/tmp/example
+----
+
+
 This makes this directory available within the Minikube VM at the path `/tmp/example`.
 
 NOTE: Some virtual machine drivers of Minikube doesn't support host mounts like this (like the `vmware` driver). You can verify this by entering the VM after startup with `minikube ssh` and check whether you see the local directories `1` and `2` in `ls /tmp/example/*`, too.