riotpiaole
3dda969784
Go's GC doesn't respect cgroup memory limits on its own, risking OOMKill under load; set GOMEMLIMIT to ~90% of each deployment's resources.limits.memory. Also switch imagePullPolicy to Always so :latest tags aren't served stale from node-local cache after a new push.
21 lines
468 B
YAML
21 lines
468 B
YAML
namespace: sqs
|
|
|
|
image:
|
|
repository: forgejo.riotpiao.homelab.com/rock/kafka-management-service-queue-operator
|
|
tag: latest
|
|
pullPolicy: Always
|
|
|
|
kafkaBrokers: "kmsvc-kafka-bootstrap.sqs.svc.cluster.local:9092"
|
|
redisAddr: "kmsvc-redis-master.sqs.svc.cluster.local:6379"
|
|
|
|
resources:
|
|
requests:
|
|
cpu: 100m
|
|
memory: 128Mi
|
|
limits:
|
|
cpu: 500m
|
|
memory: 256Mi
|
|
|
|
# See management-service/values.yaml's goMemLimit comment -- same reasoning.
|
|
goMemLimit: "230MiB"
|