-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(Kubernetes): Add JMX exporter containers to all DataHub components #2251
Conversation
@dexter-mh-lee : could you take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Details looks good! Thanks a lot for adding this!!!
One comment on using library charts to share the jmx-exporter setup component.
@@ -74,6 +79,38 @@ spec: | |||
{{- end }} | |||
resources: | |||
{{- toYaml .Values.resources | nindent 12 }} | |||
|
|||
{{- if .Values.exporters.jmx.enabled }} | |||
- name: jmx-exporter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to extract this out into a library chart? https://helm.sh/docs/topics/library_charts/ Seems like a lot of the code needs to be copy and pasted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! I'll check that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @bernardino, please let us know once you've been able to refactor this into a library chart. Looks great otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's running the build at the moment.
@dexter-mh-lee it looks waaay cleaner now! Thanks for your suggestion!
And I'm sorry for the delay.
666536a
to
06fb81f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!! Thanks for making these changes!
@bernardino There was a fix for the build issue that went in recently. The build error should go away once you merge latest master! |
06fb81f
to
57d251c
Compare
Build is now green |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks for making the changes @bernardino 👍
java $JAVA_OPTS $JMX_OPTS \ | ||
--jar jetty-util.jar \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bernardino This change is breaking prod. I think java only takes a single jar. Has this specific script been tested locally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I know what the error is, it should be
java $JAVA_OPTS $JMX_OPTS \
-jar /jetty-runner.jar \
--jar jetty-util.jar \
--jar jetty-jmx.jar \
/datahub/datahub-gms/bin/war.war
The --jar
I added is for the jetty runner, it has nothing to do with the -jar
, and in our custom run script in our helm charts the --jar
options are after the runner.jar
Fixes #2214
Added JMX exporter container to Helm charts.
Also added JVM_OPTS and JMX_OPTS to such that it is easy to configure the JMX on the original container.
Checklist