Set resources requests to 200m CPU and 320Mi memory

Signed-off-by: Stefan Prodan <[email protected]>

README.md

@@ -7,6 +7,12 @@ and monitored by [weave-gitops](https://github.com/weaveworks/weave-gitops).
 
 ![](docs/img/weave-gitops-msdemo.png)
 
+The microservices demo is composed of 20 Kubernetes Deployments
+with a total request of `200m` CPU and `320Mi` memory.
+Each microservice is managed by a dedicated Flux Kustomization, and it contains
+a podinfo instance and a redis instance,
+the podinfo instance writes to Redis every `30s`.
+
 ## Prerequisites 
 
 * A Kubernetes cluster [bootstrapped with Flux](https://fluxcd.io/docs/installation/).
@@ -128,9 +134,6 @@ To test rollout failures use a non existing version such as `99.0.0`.
 
 ## List microservices
 
-Each microservice is managed by a dedicated Flux Kustomization, and it contains
-a podinfo deployment and a Redis one, podinfo talks constantly with Redis.
-
 The above configuration will deploy the following workloads:
 
 ```console

microservice/app-deployment.yaml

@@ -57,4 +57,4 @@ spec:
               memory: 128Mi
             requests:
               cpu: 10m
-              memory: 32Mi
+              memory: 16Mi

microservice/redis-deployment.yaml

@@ -43,11 +43,11 @@ spec:
             timeoutSeconds: 5
           resources:
             limits:
-              cpu: 1000m
+              cpu: 200m
               memory: 128Mi
             requests:
               cpu: 10m
-              memory: 32Mi
+              memory: 16Mi
           volumeMounts:
             - mountPath: /var/lib/redis
               name: data