[bitnami/kafka] Update default value of heapOpts
to fit Kafka pod RAM limit while utilize its increase (#29670)
#29782
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.
Description of the change
OK, here we go:
bitnami/minideb
as base image. Unfortunately, I couldn't find any minimum requirements for this image in the README.md, therefore I assume minimal requirements of Debian itself which is 256 MB.Xmx
; b) competitive, unofficial, helm chart where we havecp-kafka.heapOptions
withXmx
set to512M
.-XX:+UseContainerSupport
is enabled by default. In this case we could benefit from setting-XX:InitialRAMPercentage
and-XX:MaxRAMPercentage
As in commit I suggest removing
-Xmx1024m -Xms1024m
and replacing it with-XX:InitialRAMPercentage=75 -XX:MaxRAMPercentage=75
. This will ensure 256 MB for the OS (768 MB*(1-0.75)=256 MB) and sort of solve the problem of scaling RAM available for Kafka with increasingContainers.kafka.Limits.memory
value.Benefits
Possible drawbacks
Kafka could be inefficient at default 768 MB*0.75=512 MB RAM.
Applicable issues
Xmx
in context of default value ofContainers.kafka.Limits.memory
#29670Additional information
This needs testing, which I cannot do with a satisfactory variety of traffic.
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm