Myasnikov DaniilandClaude Opus 4.8 1ab5f17cac fix(kafka): set entity-operator resources to avoid OOM under tenant LimitRange ...

entityOperator.topicOperator/userOperator carried no resources, so in tenant
namespaces (the LimitRange defaults containers to 128Mi) the JVM topic-operator
and user-operator are OOMKilled on startup. The entity-operator stays in
CrashLoopBackOff, KafkaTopics/KafkaUsers never reconcile, and on teardown topics
get stuck on the strimzi.io/topic-operator finalizer. Set explicit requests/limits
(256Mi/512Mi) so they no longer inherit the namespace default; add a template test.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-06-23 13:44:29 +05:00

..

dashboard-resourcemap_test.yaml

fix(kafka): gate dashboard RBAC external-bootstrap solely on external flag

2026-05-27 11:16:42 +03:00

entityoperator_template_test.yaml

fix(kafka): set entity-operator resources to avoid OOM under tenant LimitRange

2026-06-23 13:44:29 +05:00

kafka_test.yaml

test(kafka): add TLS test coverage

2026-05-27 11:16:40 +03:00

kafka_tls_test.yaml

refactor(kafka): drop null from tls.enabled schema, use kindIs invalid pattern

2026-05-27 11:16:42 +03:00

workloadmonitor_test.yaml

test: cover flux v2.8 chart fixes and wire missing test targets

2026-05-31 15:02:33 +05:00