Skip to main content

Custom CA Certificates

When You Need a Custom CA​

A custom Certificate Authority (CA) is needed when you must issue SSL/TLS certificates for internal services, devices, or users that are not reachable from the public internet.

Unlike public CAs (such as Let's Encrypt), custom CAs are managed internally and trusted only inside your organization. This is common in lab environments and secure internal deployments where:

  • Services communicate over HTTPS using internally-signed certificates
  • Your organization operates its own PKI infrastructure
  • You need to ensure all TLS traffic is validated against your trusted root certificate

Configure Custom CA in Chart Values​

For deployments in the OLIVE lab or environments using internal CAs, reference the custom CA certificate in values.yaml in two places.

Prepare the content from the CA certificate file. For example in the OLIVE lab environment the CA certificate is typically available on your master node under /usr/local/share/ca-certificates.

Step 1: Add Custom CA to Global Configuration​

At the global level in your values.yaml, add:

global:
# ... other global keys ...
customCa:
enabled: true
name: "lab-custom-ca"
bundle: |
-----BEGIN CERTIFICATE-----
MIIB/TCCAaKgAwIBAgIRALUuIvyj8ciTNJPGvzUq55IwCgYIKoZIzj0EAwIwXDEo
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
ANfGXo96JtnKl01Npc9jpn/AWWE119KOSS/HNvFXhzn1
-----END CERTIFICATE-----

Key fields:

  • enabled: Set to true to activate custom CA support
  • name: A descriptive name for your CA (e.g., lab-custom-ca, internal-pki)
  • bundle: The complete certificate content in PEM format. Paste the entire certificate including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- markers. If you have a certificate file, you can use:
cat /usr/local/share/ca-certificates/my-root-ca.crt

Step 2: Enable Custom CA Service​

Under services, add the custom-ca flag to the infra section:

services:
infra:
certificate: true
auth-proxy: false
keycloak-setup: false
tenant-setup: true
vault-secrets-setup: true
workflow-engine-postgres: true
custom-ca: true

Complete Example​

Here's a complete values snippet with custom CA enabled:

global:
tenant: 'tenant-lab'
namespace: 'tenant-lab'
clusterName: 'lab-cluster'
infraName: 'lab'
domain: 'lab.internal'
resolveTLS: true
deploymentMode: 'single-no-auth'
customCa:
enabled: true
name: "lab-internal-ca"
bundle: |
-----BEGIN CERTIFICATE-----
MIIDXTCCAkWgAwIBAgIJAKC5/XXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
... (middle lines omitted for brevity) ...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-----END CERTIFICATE-----

services:
infra:
certificate: true
auth-proxy: false
keycloak-setup: false
tenant-setup: true
vault-secrets-setup: true
workflow-engine-postgres: true
custom-ca: true
# ... rest of services configuration ...

Troubleshooting​

CA Not Loaded in Pods​

Symptom: Pods fail to connect to services with custom CA-signed certificates.

Solution:

  1. Verify the certificate format is valid PEM (starts with -----BEGIN CERTIFICATE-----)
  2. Check that custom-ca: true is enabled in services.infra
  3. Restart the affected pods after values update: kubectl rollout restart deployment/<service-name>

Certificate Expiration​

Symptom: HTTPS connections fail with "certificate has expired" errors.

Solution:

  1. Obtain the new certificate from your CA
  2. Update the bundle value in global.customCa.bundle
  3. Redeploy the chart or update the relevant ConfigMaps
  4. Restart affected pods