wip

Author: Antonio Cappiello

README.md

@@ -1294,7 +1294,7 @@ You can configure multiple such initContainers as well, like how we did for mult
 
 If any of the initContainers fail to complete, Kubernetes restarts the Pod repeatedly until the Init Container succeeds.
 
-## Cluster Maintenance
+## Cluster Mainteance
 
 Topics: operating systems upgrades, losing a node from the cluster, apply patches, kubernetes releases and versions, best practices around upgrading.
 Perform an end-to-end upgrade on a cluster, and also apply a disaster recovery scenario.
@@ -1330,7 +1330,7 @@ First you upgrade your master node, and then the worker nodes. When upgrading th
 
 But first you have to update kubeadm:
 
-```md
+```
 apt-get upgrade -y kubeadm=1.12.0-00
 kubeadm upgrade apply v1.12.0
 # then upgrade on worker nodes as well

pod.k8s.yaml

@@ -0,0 +1,37 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: "i"
+  namespace: default
+  labels:
+    app: "myapp"
+spec:
+  containers:
+  - name: myapp
+    image: "debian-slim:latest"
+    resources:
+      limits:
+        cpu: 200m
+        memory: 500Mi
+      requests:
+        cpu: 100m
+        memory: 200Mi
+    env:
+    - name: DB_HOST
+      valueFrom:
+        configMapKeyRef:
+          name: myapp
+          key: DB_HOST
+    ports:
+    - containerPort: 80
+      name: http
+    volumeMounts:
+    - name: localtime
+      mountPath: /etc/localtime
+  volumes:
+    - name: localtime
+      hostPath:
+        path: /usr/share/zoneinfo/Asia/Taipei
+  restartPolicy: Always
+---
+