added kubernetes lab

Author: imShakil

kubernetes/09.md

@@ -2,15 +2,96 @@
 
 The Nautilus DevOps team needs a time check pod created in a specific Kubernetes namespace for logging purposes. Initially, it's for testing, but it may be integrated into an existing cluster later. Here's what's required:
 
-Create a pod called time-check in the devops namespace. The pod should contain a container named time-check, utilizing the busybox image with the latest tag (specify as busybox:latest).
+Create a pod called `time-check` in the `nautilus` namespace. The pod should contain a container named `time-check`, utilizing the `busybox` image with the latest tag (specify as `busybox:latest`).
 
-- Create a config map named time-config with the data TIME_FREQ=10 in the same namespace.
+- Create a config map named `time-config` with the data `TIME_FREQ=7` in the same namespace.
 
-- Configure the time-check container to execute the command: while true; do date; sleep $TIME_FREQ;done. Ensure the result is written /opt/finance/time/time-check.log. Also, add an environmental variable TIME_FREQ in the container, fetching its value from the config map TIME_FREQ key.
+- Configure the `time-check` container to execute the command: `while true; do date; sleep $TIME_FREQ;done`. Ensure the result is written `/opt/finance/time/time-check.log`. Also, add an environmental variable `TIME_FREQ` in the container, fetching its value from the config map `TIME_FREQ` key.
 
-- Create a volume log-volume and mount it at /opt/finance/time within the container.
+- Create a volume `log-volume` and mount it at `/opt/finance/time` within the container.
 
 > Note: The kubectl utility on jump_host is configured to operate with the Kubernetes cluster.
 
 ## Steps
 
+1. Let's check namespace and create `nautilus` namespace
+
+    ```sh
+    kubectl get ns
+    kubectl create ns nautilus
+    ```
+
+2. Let's create the `k3s.yml` file using [this contents](./09.yml)
+
+    ```YAML
+    # ConfigMap
+    apiVersion: v1
+    kind: ConfigMap
+    metadata:
+    name: time-config
+    namespace: nautilus
+    data:
+    TIME_FREQ: "7"
+
+    ---
+
+    apiVersion: v1
+    kind: Pod
+    metadata:
+    name: time-check
+    namespace: nautilus
+    labels:
+        app: time-check
+    spec:
+    containers:
+    - name: time-check
+        image: busybox:latest
+        command: ["/bin/sh", "-c", "while true; do date >> /opt/finance/time/time-check.log; sleep ${TIME_FREQ}; done"]
+        env:
+        - name: TIME_FREQ
+        valueFrom:
+            configMapKeyRef:
+            name: time-config
+            key: TIME_FREQ
+        volumeMounts:
+        - name: log-volume
+        mountPath: /opt/finance/time
+        resources:
+        limits:
+            cpu: 100m
+            memory: 128Mi
+        requests:
+            cpu: 100m
+            memory: 128Mi
+    volumes:
+    - name: log-volume
+        emptyDir: {}
+    ```
+
+3. Let's run the following command:
+
+    ```sh
+    kubectl apply -f k3s.yml
+    ```
+
+    > It will create configmap and pod
+
+4. We can verify
+
+    ```sh
+    kubectl get pods -n nautilus
+    ```
+
+    ```shell
+    kubectl get pods -n nautilus
+    NAME         READY   STATUS    RESTARTS   AGE
+    time-check   1/1     Running   0          19s
+    ```
+
+5. Verify log:
+    To verify log, we can execute the container of the pods and inside we can check our log files.
+
+    ```sh
+    kubectl exec -it time-check -n nautilus /bin/sh
+    cat /opt/finance/time/time-check.log
+    ```

kubernetes/09.yml

@@ -0,0 +1,42 @@
+# ConfigMap
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: time-config
+  namespace: nautilus
+data:
+  TIME_FREQ: "7"
+
+---
+
+apiVersion: v1
+kind: Pod
+metadata:
+  name: time-check
+  namespace: nautilus
+  labels:
+    app: time-check
+spec:
+  containers:
+  - name: time-check
+    image: busybox:latest
+    command: ["/bin/sh", "-c", "while true; do date >> /opt/finance/time/time-check.log; sleep ${TIME_FREQ}; done"]
+    env:
+    - name: TIME_FREQ
+      valueFrom:
+        configMapKeyRef:
+          name: time-config
+          key: TIME_FREQ
+    volumeMounts:
+    - name: log-volume
+      mountPath: /opt/finance/time
+    resources:
+      limits:
+        cpu: 100m
+        memory: 128Mi
+      requests:
+        cpu: 100m
+        memory: 128Mi
+  volumes:
+  - name: log-volume
+    emptyDir: {}

projects/wp-high-availability-on-aws/README.md

@@ -0,0 +1,2 @@
+# Design and Deploy a Two-Tier Wordpress Application High Availabiltiy on AWS Cloud
+