Merge pull request #1 from LuckySB/res_reduce

reduce resource usage

practice/11.deployment-alternative/2.statefulset/rabbitmq-statefulset/statefulset.yaml

@@ -41,8 +41,8 @@ spec:
               cpu: 1000m
               memory: 1024Mi
             requests:
-              cpu: 250m
-              memory: 512Mi
+              cpu: 10m
+              memory: 256Mi
           livenessProbe:
             exec:
               command: ["rabbitmqctl", "status"]
@@ -89,4 +89,4 @@ spec:
         accessModes: ["ReadWriteOnce"]
         resources:
           requests:
-            storage: 1Gi
+            storage: 20Mi

practice/2.application-abstractions/4.resources/deployment-with-resources.yaml

@@ -21,7 +21,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 100m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/4.saving-configurations/1.env/README.md

@@ -5,7 +5,7 @@
 Для этого выполним команду:
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/1.env/deployment-with-env.yaml
+kubectl apply -f ~/slurm/practice/4.saving-configurations/1.env/deployment-with-env.yaml
 ```
 
 2) Проверяем результат
@@ -26,8 +26,8 @@ Environment:
 3) Создаем configmap
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/1.env/configmap.yaml
-kubectl apply -f ~/slurm/practice/3.saving-configurations/1.env/deployment-with-env-cm.yaml
+kubectl apply -f ~/slurm/practice/4.saving-configurations/1.env/configmap.yaml
+kubectl apply -f ~/slurm/practice/4.saving-configurations/1.env/deployment-with-env-cm.yaml
 ```
 
 4) Проверяем результат

practice/4.saving-configurations/1.env/deployment-with-env-cm.yaml

@@ -31,7 +31,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/4.saving-configurations/1.env/deployment-with-env.yaml

@@ -28,7 +28,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/4.saving-configurations/2.secret/README.md

@@ -15,7 +15,7 @@ kubectl get secret test -o yaml
 Для этого выполним команду:
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/2.secret/deployment-with-secret.yaml
+kubectl apply -f ~/slurm/practice/4.saving-configurations/2.secret/deployment-with-secret.yaml
 ```
 
 3) Проверяем результат
@@ -37,7 +37,7 @@ Environment:
 4) Применяем манифест с секретом
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/2.secret/secret.yaml
+kubectl apply -f ~/slurm/practice/4.saving-configurations/2.secret/secret.yaml
 ```
 
 5) Проверяем что в секрете

practice/4.saving-configurations/2.secret/deployment-with-secret.yaml

@@ -36,7 +36,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/4.saving-configurations/3.configmap/README.md

@@ -5,7 +5,7 @@
 Для этого выполним команду:
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/3.configmap/
+kubectl apply -f ~/slurm/practice/4.saving-configurations/3.configmap/
 ```
 
 2) Проверяем

practice/4.saving-configurations/3.configmap/deployment-with-configmap.yaml

@@ -25,7 +25,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/4.saving-configurations/4.downward/README.md

@@ -5,7 +5,7 @@
 Для этого выполним команду:
 
 ```bash
-kubectl apply -f ~/slurm/practice/3.saving-configurations/4.downward/
+kubectl apply -f ~/slurm/practice/4.saving-configurations/4.downward/
 ```
 
 2) Смотрим переменные окружения в контейнере

practice/4.saving-configurations/4.downward/deployment-with-downward-api.yaml

@@ -57,7 +57,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/5.saving-data/1.hostpath/README.md

@@ -3,7 +3,7 @@
 1) Применяем манифест
 
 ```bash
-kubectl apply -f ~/slurm/practice/4.saving-data/1.hostpath/
+kubectl apply -f ~/slurm/practice/5.saving-data/1.hostpath/
 
 kubectl get pod
 kubectl get all

practice/5.saving-data/1.hostpath/deployment.yaml

@@ -25,7 +25,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/5.saving-data/2.emptydir/README.md

@@ -3,7 +3,7 @@
 1) Применяем манифест
 
 ```bash
-kubectl apply -f ~/slurm/practice/4.saving-data/2.emptydir/
+kubectl apply -f ~/slurm/practice/5.saving-data/2.emptydir/
 ```
 
 2) Заходим в под и создаем файлик на томе empty dir

practice/5.saving-data/2.emptydir/deployment.yaml

@@ -25,7 +25,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/5.saving-data/3.pvc/README.md

@@ -3,7 +3,7 @@
 1) Применяем манифест pvc.yml
 
 ```bash
-kubectl apply -f ~/slurm/practice/4.saving-data/3.pvc/pvc.yaml
+kubectl apply -f ~/slurm/practice/5.saving-data/3.pvc/pvc.yaml
 
 kubectl get pvc
 kubectl get pv
@@ -12,7 +12,7 @@ kubectl get pv
 2) Запустим приложение, использующее PV
 
 ```bash
-kubectl apply -f ~/slurm/practice/4.saving-data/3.pvc/
+kubectl apply -f ~/slurm/practice/5.saving-data/3.pvc/
 ```
 
 3) Посмотрим describe и смонтированные тома в контейнере
@@ -25,5 +25,5 @@ kubectl exec -it fileshare-<TAB> -- df -h
 4) Очищаем
 
 ```bash
-kubectl delete -f ~/slurm/practice/4.saving-data/3.pvc/
+kubectl delete -f ~/slurm/practice/5.saving-data/3.pvc/
 ```

practice/5.saving-data/3.pvc/deployment.yaml

@@ -32,7 +32,7 @@ spec:
         - containerPort: 80
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m

practice/5.saving-data/3.pvc/pvc.yaml

@@ -8,4 +8,4 @@ spec:
   - ReadWriteMany
   resources:
     requests:
-      storage: 1Gi
+      storage: 10Mi

practice/7.network-abstractions/1.probes/deployment-with-stuff.yaml

@@ -49,7 +49,7 @@ spec:
           periodSeconds: 10
         resources:
           requests:
-            cpu: 50m
+            cpu: 10m
             memory: 100Mi
           limits:
             cpu: 100m