Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Helm Chart #43

Merged
merged 7 commits into from
Oct 29, 2019
Merged

Conversation

ADefossez-Zenika
Copy link
Contributor

Hi folks, I have added some environment variables to the Helm Chart.
Is it OK for you ?

@@ -38,8 +38,34 @@ spec:
value: "{{ .Values.kafka.keystore }}"
- name: JVM_OPTS
value: "{{ .Values.jvm.opts }}"
{{- if .Values.jmx.port }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need the if and end conditional blocks? Can't we just set the value, assuming there is a default in values.yaml?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Threre is already default values in kafdrop application.yaml and docker entrypoint (kafdrop.sh), so i prefer not overriding them with some others/null values. It seems cleaner to me.
If i leave it as is, it's not so clean, but if i remove them, we need to synchronize default values (values.yaml and application.yaml/kafdrop.sh)

What is your opinion ? Doesn’t matter for me ;)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to avoid conditional macros and just deal with defaults that are clearly stated in values.yaml, so that anyone who wants to know what an unspecified value will default to can check values.yaml.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problemo, i'm making changes.

@@ -10,14 +10,22 @@ kafka:
properties: ""
truststore: ""
keystore: ""
properties_file: ""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest we use camel-casing here to be consistent with the other entries in values.yaml. I.e. propertiesFile.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right.

- name: SERVER_SERVLET_CONTEXTPATH
value: "{{ .Values.server.servlet.contextPath }}"
{{- end }}
{{- if .Values.kafka.properties_file }}
- name: KAFKA_PROPERTIES_FILE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, is there a particular reason why the file location needs to be configurable? When you're using Helm (or any Docker setup), you would be passing in the contents of the properties/truststore/keystore files. Does it matter where they end up being placed inside the container?

I can see how configuring these locations may be useful or necessary when running directly from a Jar. But in what context would these be overridden in Docker?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my case, i'm running Kafdrop in a very secure environment, i can't write files anywhere i want to. I need this location to be configurable, so kafdrop.sh can write this file somewhere else than / (root).

@ekoutanov ekoutanov merged commit 5c7f1a0 into obsidiandynamics:master Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants