added extra content

Author: vijayboopathy

exercises/140-ingress.md

@@ -0,0 +1,39 @@
+#### 1. Create a nginx ingress controller by following the documentation.
+`Reference`: [Nginx ingress](https://kubernetes.github.io/ingress-nginx/deploy/#generic-deployment)
+
+#### 2. Use the nginx ingress to with the following properties for the deployment give below. Create the missing components to expose this deployment.
+```
+[ingress-details]
+ingress controller: nginx
+domain name: mogambo.com
+path: /
+service: frontend
+service port: 80
+```
+```
+[frontend-deployment]
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: frontend
+spec:
+  replicas: 2
+  template:
+    metadata:
+      labels:
+        app: front-end
+    spec:
+      containers:
+      - image: schoolofdevops/frontend:latest
+        imagePullPolicy: Always
+        name: front-end
+        ports:
+        - containerPort: 8079
+          protocol: TCP
+```
+
+#### 3. Create a basic authentication for the frontend deployment with the following parameters with nginx ingress controller.
+```
+username: serviceadmin
+password: sup3rs3cr3t
+```

exercises/150-network-policies.md

@@ -0,0 +1 @@
+#### 1. Create a network policy manifest which allows 

exercises/170-rbac.yml

@@ -0,0 +1,18 @@
+#### 1. Generate certificates for the follwoing user table
+| User  | Group  | Namespace  | Resources  | Access Types  |
+|--:|--:|--:|--:|---|
+| Mike  | Ops  | all  | all  | get, list, watch, update, patch, create, delete, deletecollection  |
+| Vitos  | Test  | test  | all  | get, list, watch, update, patch, create, delete  |
+| Dimash  | Dev  | dev  | all  | get, list, watch  |
+
+#### 2. Create kubeconfig files and set contexts for the above mentioned table.
+
+#### 3. Grant extra priviliges for the user `Dimash` to `get,list and watch` resources on `test` namespace.
+
+#### 4. Create a cluster role with the following properties.
+```
+name: config-reader
+resources: configmaps
+verbs: get, watch and list
+```
+Create a Cluster Role Binding which allows user `Dave` to use this Cluster Role.

exercises/180-advancec-pod.md

@@ -0,0 +1,82 @@
+#### 1. In your Kubernetes cluster, Label one node with the label `frontend` and schedule the frontend deployment in the frontend node.
+```
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: frontend
+spec:
+  replicas: 3
+  template:
+    metadata:
+      labels:
+        app: frontend
+        role: ui
+    spec:
+      containers:
+      - image: schoolofdevops/frontend:latest
+        imagePullPolicy: Always
+        name: front-end
+        ports:
+        - containerPort: 8079
+          protocol: TCP
+        resources:
+          requests:
+            memory: "128Mi"
+            cpu: "250m"
+          limits:
+            memory: "256Mi"
+            cpu: "500m"
+    [...]
+```
+
+#### 2. Schedule the catalogue pods in the same node as frontend pod.
+```
+kind: Deployment
+metadata:
+  name: catalogue
+  labels:
+    app: catalogue
+    env: dev
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: catalogue
+  template:
+    metadata:
+      labels:
+        app: catalogue
+        env: dev
+    spec:
+      containers:
+        - name: catalogue
+          image: schoolofdevops/catalogue:v2
+          imagePullPolicy: Always
+          ports:
+            - containerPort: 80
+```
+
+#### 3. Make one of the node(ex. node 2) as unschedulable. Only carts pods should be schedulable on that node.
+```
+apiVersion: apps/v1beta1
+kind: Deployment
+metadata:
+  name: carts
+  labels:
+    app: carts
+    env: dev
+spec:
+  replicas: 1
+  template:
+    metadata:
+      labels:
+        app: carts
+        env: dev
+    spec:
+      containers:
+        - name: carts
+          image: schoolofdevops/carts
+          imagePullPolicy: Always
+          ports:
+            - containerPort: 80
+```