-
Notifications
You must be signed in to change notification settings - Fork 134
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
Add helm value for custom jmx jar location when using other jmx init container images #846
Conversation
@corang thanks, indeed using a different image (with a different jmx jar location) can be problematic without this fix. We'll release 1.20.2 this week. |
Do you want me to try to fix the output files for testing? @bianchi2 |
@corang you may run this command
and commit changed expected output files. |
@bianchi2 If I can I would suggest adding |
@corang ah, right. I just had the deps locally so it worked for me because of the volume mount. Thanks for fixing the tests! |
Hey @bianchi2, I was looking to use this feature, but it looks like the subchart hasn't been released to reflect this change in the consuming charts. Is there an eta on this being released? |
@Michael-Kruggel indeed 🤦 common was never released. We'll cut a new release this week. UPDATE: 1.21.3 is out (bumped common dependency version to 1.2.7) |
Since the first argument to the copy for the initcontainer is hardcoded, it allows only the bitnami image to be used. Making this value based allows for other images to be used instead.