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.

Sign up for GitHub

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

Jump to bottom

Optionally Start up JMX via values.yaml for production debugging purposes #1757

Open
artntek opened this issue Dec 7, 2023 · 1 comment
Open

Optionally Start up JMX via values.yaml for production debugging purposes #1757

artntek opened this issue Dec 7, 2023 · 1 comment
Labels
k8s Kubernetes/Helm Related
Milestone
3.1.0

Comments

@artntek
Copy link
Contributor

artntek commented Dec 7, 2023

Optionally Start up JMX via values.yaml for production debugging purposes
@artntek artntek added this to the 3.1.0 milestone Dec 7, 2023
@artntek artntek added the k8s Kubernetes/Helm Related label Dec 7, 2023
@mbjones
Copy link
Member

mbjones commented Dec 7, 2023

This would be great, and useful, especially if one coudl do a k8s rolling upgrade to switch jmx=true without much (any?) downtime. But, this is definitely in the nice-to-have category and I don't think it should slow down or block release and deployment of 3.0.0.

@artntek artntek mentioned this issue May 9, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
k8s Kubernetes/Helm Related
Projects
None yet
Milestone
3.1.0
Development

No branches or pull requests
2 participants
@mbjones @artntek