imfreedom/k8s-cluster

Parents 0891fc87e948
Children dbe1665778da
Add resource limits to all imf deployments and fix the minio deployment that's been broken for a bit
--- a/50-data.imfreedom.org.yaml Sat May 04 15:08:00 2019 -0500
+++ b/50-data.imfreedom.org.yaml Sat May 04 16:03:40 2019 -0500
@@ -76,12 +76,12 @@
spec:
containers:
- name: minio
- image: minio/minio:latest
+ image: minio/minio:RELEASE.2019-05-02T19-07-09Z
imagePullPolicy: Always
livenessProbe:
exec:
command:
- - /usr/bin/healthcheck.sh
+ - /usr/bin/healthcheck
command:
- minio
- server
@@ -92,6 +92,13 @@
- mountPath: /data
name: data
readOnly: false
+ resources:
+ limits:
+ cpu: 200m
+ memory: 128Mi
+ requests:
+ cpu: 100m
+ memory: 96Mi
volumes:
- name: data
persistentVolumeClaim:
--- a/50-imfreedom.org.yaml Sat May 04 15:08:00 2019 -0500
+++ b/50-imfreedom.org.yaml Sat May 04 16:03:40 2019 -0500
@@ -72,7 +72,7 @@
labels:
app: www
spec:
- replicas: 1
+ replicas: 2
selector:
matchLabels:
app: www
@@ -87,5 +87,12 @@
imagePullPolicy: Always
ports:
- containerPort: 80
+ resources:
+ limits:
+ cpu: 200m
+ memory: 128Mi
+ requests:
+ cpu: 100m
+ memory: 96Mi
---
--- a/50-ldap.imfreedom.org.yaml Sat May 04 15:08:00 2019 -0500
+++ b/50-ldap.imfreedom.org.yaml Sat May 04 16:03:40 2019 -0500
@@ -61,6 +61,13 @@
- mountPath: /var/lib/ldap
name: data
readOnly: false
+ resources:
+ limits:
+ cpu: 400m
+ memory: 1024Mi
+ requests:
+ cpu: 200m
+ memory: 512Mi
securityContext:
fsGroup: 101
runAsUser: 101