[helm-chart] Clarify that configuration
and extraEnv
values cannot be used simultaneously
#1203
SergiyKolesnikov
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
Not exactly true :) Feel free to add this clarification on the docs and values in a PR, it's will be merged quickly. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The documentation (and a comment in the values.yaml) should mention that the
configuration
andextraEnv
(withAKHQ_CONFIGURATION
) values cannot be set simultaneously, because the AKHQ container will fail to start.The default
helm/akhq/values.yaml
setsconfiguration
value. If now we also setAKHQ_CONFIGURATION
in theextraEnv
value, the AKHQ container will fail to start with the error:docker-entrypoint.sh
errors out because it tries to write the contents of theAKHQ_CONFIGURATION
environment variable to the read-only/app/application.yml
file. The file is read-only because a ConfigMap (with settings from theconfiguration
value) has been mounted into it already.For
extraEnv
withAKHQ_CONFIGURATION
to work, theconfiguration
value must be set tofalse
, so that the ConfigMap is not mounted and/app/application.yml
can be written. For example:Beta Was this translation helpful? Give feedback.
All reactions