Managing Certificates
The OpenShell gateway uses mTLS certificates for transport between the gateway and sandbox supervisors. These certificates are not Kubernetes user authentication; configure OIDC or a trusted access proxy for user access. The Helm chart supports two ways to provision and manage the certificate bundle:
The rest of this page covers switching to cert-manager. The built-in mode requires no configuration.
When certManager.enabled=true, cert-manager owns TLS certificate generation.
The chart still runs a JWT-only initialization hook because cert-manager does
not create the sandbox JWT signing Secret required by the gateway. This
cert-manager precedence applies even if pkiInitJob.enabled remains true.
Install cert-manager
Add the Jetstack Helm repository and install cert-manager with CRD support enabled:
Verify the cert-manager pods are running:
Install OpenShell with cert-manager PKI
Pass the cert-manager values override when installing or upgrading the chart:
The chart creates a self-signed CA, issues server and client certificates from it, and cert-manager handles renewal before expiry.
The chart also runs a pre-install hook in JWT-only mode to create the gateway’s
sandbox JWT signing Secret. That Secret is separate from the cert-manager TLS
certificate Secrets and is mounted at /etc/openshell-jwt.
Next Steps
Return to Setup to complete the installation.