How can I deploy n8n on EKS with a custom root certificate to fix SSL errors?

Below is one approach to adding your root certificate on EKS:

1. Create a Kubernetes Secret or ConfigMap with your certificate files
   If your certificate(s) (or CA bundle) are stored locally (for example, in a folder called pki), you can create a Secret from those files:

   BASHCopied
   kubectl create secret generic my-certificates --from-file=pki/

2. Mount the certificates into the n8n Pod
   In your n8n Deployment manifest, add a volume that sources from the secret and mount it at /opt/custom-certificates. For example:

   YAMLCopied
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: n8n
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: n8n
     template:
       metadata:
         labels:
           app: n8n
       spec:
         volumes:
           - name: custom-certificates
             secret:
               secretName: my-certificates
         initContainers:
           - name: fix-cert-permissions
             image: busybox
             command: ["sh", "-c", "chown -R 1000:1000 /opt/custom-certificates"]
             volumeMounts:
               - name: custom-certificates
                 mountPath: /opt/custom-certificates
         containers:
           - name: n8n
             image: docker.n8n.io/n8nio/n8n
             ports:
               - containerPort: 5678
             volumeMounts:
               - name: custom-certificates
                 mountPath: /opt/custom-certificates

   A few points to note:

   • The certificate files will be available at /opt/custom-certificates inside the container. n8n is configured to automatically trust certificates placed there.
   • The included initContainer fixes permissions by changing ownership to the n8n user (UID 1000). This step is similar to the manual Docker CLI command provided in the documentation.

3. Deploy the updated manifest
   Apply the changes to your EKS cluster:

   BASHCopied
   kubectl apply -f your-deployment-file.yaml

With this setup, n8n should be able to use your custom (root) certificate during SSL communications, avoiding the certificate chain errors and allowing you to receive your license.