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
We're using docs documentserver deployed by Helm Chart inside our on-primeses kubernetes cluster and all things are working great. A feature was requested and we created a custom plugin. In our local dev machine, using docker version, the custom plugin was added manually, tested and approved. When we started to deploy in the staging server, we needed to extend the docker image and copy the plugin folder.
Why not create a ConfigMap with binaryData pointing to plugin.tar.gz, and inside a sidecar in docserver, with an extra volume we extract plugin inside sdkjs-plugins?
We're using docs documentserver deployed by Helm Chart inside our on-primeses kubernetes cluster and all things are working great. A feature was requested and we created a custom plugin. In our local dev machine, using docker version, the custom plugin was added manually, tested and approved. When we started to deploy in the staging server, we needed to extend the docker image and copy the plugin folder.
Why not create a ConfigMap with binaryData pointing to plugin.tar.gz, and inside a sidecar in docserver, with an extra volume we extract plugin inside sdkjs-plugins?
My idea
ConfigMap.yaml
Docs helm chart Values.yaml:
The text was updated successfully, but these errors were encountered: