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
Passbolt container Image uses /etc/ssl/certs/certificate.crt and /etc/ssl/certs/certificate.key (see contents of /etc/nginx/snippets/passbolt-ssl.conf file).
However helm chart mount internal tls certificate in '/etc/ssl/certs/passbolt/server.crt' and '/etc/ssl/certs/passbolt/server-key.pem'.
Since It is common to use tls.key and tls.crt as the keys in kubernetes tls secrets, I propose to use a projected volume to be able to mount the kubernetes secret in the target path: /etc/ssl/certs/certificate.crt and /etc/ssl/certs/certificate.key
Related with #80
Passbolt container Image uses
/etc/ssl/certs/certificate.crt
and/etc/ssl/certs/certificate.key
(see contents of /etc/nginx/snippets/passbolt-ssl.conf file).However helm chart mount internal tls certificate in '/etc/ssl/certs/passbolt/server.crt' and '/etc/ssl/certs/passbolt/server-key.pem'.
charts-passbolt/templates/deployment.yaml
Line 148 in 4bde003
Since It is common to use
tls.key
andtls.crt
as the keys in kubernetes tls secrets, I propose to use a projected volume to be able to mount the kubernetes secret in the target path:/etc/ssl/certs/certificate.crt
and/etc/ssl/certs/certificate.key
example:
The helper that generate the internal-certs must also be updated to use
tls.crt
andtls.key
.charts-passbolt/templates/_helpers.tpl
Lines 267 to 268 in 4bde003
With this changes, I was able to deploy passbolt with GatewayAPI TLSPassthrough and an external certificate provided by cert-manager.
If you found it a good solution I can make a pull-request with the changes.
The text was updated successfully, but these errors were encountered: