[docs] Update to chart [email protected]

EOEPCA · Sep 22, 2023 · 36eca48 · 36eca48
1 parent 1a00faa
commit 36eca48
Showing 1 changed file with 21 additions and 1 deletion.
diff --git a/docs/eoepca/login-service.md b/docs/eoepca/login-service.md
@@ -9,7 +9,7 @@ The _Login Service_ is deployed via the `login-service` helm chart from the [EOE
 The chart is configured via values that are fully documented in the [README for the `login-service` chart](https://github.com/EOEPCA/helm-charts/tree/main/charts/login-service#readme).
 
 ```bash
-helm install --version 1.2.1 --values login-service-values.yaml \
+helm install --version 1.2.8 --values login-service-values.yaml \
   --repo https://eoepca.github.io/helm-charts \
   login-service login-service
 ```
@@ -45,12 +45,29 @@ config:
 opendj:
   volumeClaim:
     name: eoepca-userman-pvc
+  resources:
+    requests:
+      cpu: 100m
+      memory: 300Mi
 oxauth:
   volumeClaim:
     name: eoepca-userman-pvc
+  resources:
+    requests:
+      cpu: 100m
+      memory: 1000Mi
 oxtrust:
   volumeClaim:
     name: eoepca-userman-pvc
+  resources: 
+    requests:
+      cpu: 100m
+      memory: 1500Mi
+oxpassport:
+  resources:
+    requests:
+      cpu: 100m
+      memory: 100Mi
 nginx:
   ingress:
     annotations:
@@ -63,6 +80,9 @@ nginx:
         secretName: login-service-tls
 ```
 
+!!! note
+    The `resources:` above have been limited for the benefit of a minikube deployment. For a production deployment the values should be tuned (upwards) according to operational needs.
+
 ## Login Service Usage
 
 Once the deployment has been completed successfully, the Login Service is accessed at the endpoint `https://auth.<domain>/`, configured by your domain - e.g. [https://auth.192-168-49-2.nip.io/](https://auth.192-168-49-2.nip.io/).