You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After uploading an SSL cert through web dashboard, and if the pod restarts, the cert file does not persist.
To Reproduce
Steps to reproduce the behavior:
Setup kubernetes deployment
Upload SSL cert for https/host connection through instance web interface
If pod is restarted for whatever reason, the cert file does not persist
I understand the app is built for a native install, I mainly want to get a confirmation that for a successful deployment, whether we need to embed the cert (similar to root.WAR file) when we create our own image.
The text was updated successfully, but these errors were encountered:
So giving this a quick test on 10.42.1 it looks like the manual upload goes to /usr/local/tomcat so that wouldn't work for persistence when using the JamfPro web ui to upload a certificate. I just added support for overriding the server.xml from the docker build or a mounted volume so that would be the tact to take in order to achieve persistence of a certificate.
Describe the bug
After uploading an SSL cert through web dashboard, and if the pod restarts, the cert file does not persist.
To Reproduce
Steps to reproduce the behavior:
I understand the app is built for a native install, I mainly want to get a confirmation that for a successful deployment, whether we need to embed the cert (similar to root.WAR file) when we create our own image.
The text was updated successfully, but these errors were encountered: