Expose Kafka Connect jvmOptions via chart values#355
Open
clintonium-119 wants to merge 2 commits into
Open
Conversation
…namic-heap fallback
clintonium-119
changed the title
clintonium-119
changed the title
toddkazakov
approved these changes
May 8, 2026
Contributor
toddkazakov
left a comment
toddkazakov
left a comment
There was a problem hiding this comment.
Apologies for the downstream effect. This is likely caused by the changes I did yesterday that add memory requests/limits. Without those strimzi doesn't set STRIMZI_DYNAMIC_HEAP_PERCENTAGE.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.Values.jvmOptionsthrough toKafkaConnect.spec.jvmOptions. Default is empty ({}), so existing deployments areunaffected.
Motivation
Strimzi sizes the Kafka Connect JVM heap as a percentage of the cgroup memory
limit (
STRIMZI_DYNAMIC_HEAP_PERCENTAGE, default 75). That works well inproduction but is environment-sensitive: on some host kernel + container-runtime
combinations the cgroup-v2 read fails and the script falls back to host
/proc/meminfo, requesting a heap size larger than the container can hold andSIGKILLing the JVM (OOMKilled, exit 137) shortly after startup.
Exposing
jvmOptionslets affected environments (currently observed in localkind-based dev stacks on newer kernels) pin
-Xms/-Xmxexplicitly without achart fork. The accompanying tiltronic PR documents the workaround for local dev.
Related PR: https://github.com/tidepool-org/tiltronic/pull/42