- to prevent throttling Removed CPU limits from all infrastructure components while keeping memory limits for protection: - cnpg: removed 500m CPU limit - external-secrets: removed 200m, 100m CPU limits (operator, webhook, certController) - falco: removed 500m CPU limit (falcosidekick webui) - vault: removed 500m CPU limit - velero: removed 500m, 1000m CPU limits (server, node-agent) Benefits: - ✅ Prevents CPU throttling - ✅ Better performance and lower latency - ✅ More efficient resource utilization - ✅ Simpler management (only requests to tune) Memory limits are kept to prevent memory leaks and OOM issues.
35 lines
672 B
YAML
35 lines
672 B
YAML
# PostgreSQL (Development) Helm Values
|
|
# Chart: https://github.com/bitnami/charts/tree/main/bitnami/postgresql
|
|
# Single instance for development
|
|
|
|
fullnameOverride: postgresql-dev
|
|
|
|
image:
|
|
tag: latest
|
|
|
|
architecture: standalone
|
|
|
|
auth:
|
|
existingSecret: postgresql-password-dev
|
|
secretKeys:
|
|
adminPasswordKey: postgres-password
|
|
userPasswordKey: password
|
|
username: bluemayne
|
|
database: postgres
|
|
|
|
persistence:
|
|
enabled: true
|
|
size: 10Gi
|
|
storageClass: local-path
|
|
|
|
resources:
|
|
requests:
|
|
memory: "256Mi"
|
|
cpu: "30m" # Reduced to 30% of original (100m -> 30m)
|
|
limits:
|
|
# cpu: removed to prevent throttling
|
|
memory: "1Gi"
|
|
|
|
metrics:
|
|
enabled: false
|