Skip to content

Commit 5a7e2d5

Browse files
committed
fix(harbor): give the nginx proxy explicit resources so it survives the tenant LimitRange
With expose.type=clusterIP the goharbor chart deploys an nginx proxy pod, but the chart set no resources for it. In a tenant namespace the LimitRange defaults any container without resources to a 128Mi memory limit, so the proxy is OOMKilled (exit 137) and Harbor never comes up. Set the nginx proxy to t1.small (512Mi) and bump the portal (also nginx-based) from t1.nano (128Mi) to t1.micro (256Mi) for the same reason. Signed-off-by: IvanHunters <[email protected]>
1 parent 41f92ec commit 5a7e2d5

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎packages/apps/harbor/templates/harbor.yaml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -191,8 +191,10 @@ spec:
191191
{{- end }}
192192
{{- end }}
193193
{{- end }}
194+
nginx:
195+
resources: {{- include "cozy-lib.resources.defaultingSanitize" (list "t1.small" (dict) $) | nindent 10 }}
194196
portal:
195-
resources: {{- include "cozy-lib.resources.defaultingSanitize" (list "t1.nano" (dict) $) | nindent 10 }}
197+
resources: {{- include "cozy-lib.resources.defaultingSanitize" (list "t1.micro" (dict) $) | nindent 10 }}
196198
core:
197199
{{- if and $tokenKey $tokenCert }}
198200
tokenKey: {{ $tokenKey | quote }}

0 commit comments

Comments
 (0)