search

8gears / n8n-helm-chart

A Kubernetes Helm chart for n8n a Workflow Automation Tool. Easily automate tasks across different services.
https://artifacthub.io/packages/helm/open-8gears/n8n
Apache License 2.0
187 stars 97 forks source link

Pod does not start #48

Closed dolohow closed 1 year ago

dolohow commented 1 year ago

values.yaml:

config:
  database:
    type: postgresdb
    postgresdb:
      host: n8n-db
      user: n8n
  executions:
    pruneData: true
  generic:
    timezone: Europe/Warsaw
  host: CUT
  protocol: https
  userManagement:
    emails:
      smtp:
        host: <CUT>
        port: 587
        auth:
          user: <CUT>
        sender: "n8n <CUT>"
n8n:
  encryption_key: <CUT>
secret:
  database:
    postgresdb:
      password: <CUT>
  userManagement:
    emails:
      smtp:
        auth:
          pass: <CUT>
image:
  tag: 1.0.5
ingress:
  enabled: true
  annotations:
    acme.cert-manager.io/http01-ingress-class: traefik
    cert-manager.io/cluster-issuer: letsencrypt
  hosts:
    - host: CUT
      paths: [/]
  tls:
    - secretName: n8n-cert
      hosts:
        - CUT
resources:
  requests:
    cpu: 100m
    memory: 512Mi
  limits:
    cpu: 1000m
    memory: 1024Mi
> kubectl logs n8n...
Loading config overwrites [ '/n8n-config/config.json', '/n8n-secret/secret.json' ]
UserSettings were generated and saved to: /home/node/.n8n/config
> kubectl describe n8n...
  Normal   Scheduled  12m                   default-scheduler  Successfully assigned n8n/n8n to k1
  Normal   Pulled     11m (x4 over 12m)     kubelet            Container image "n8nio/n8n:1.0.5" already present on machine
  Normal   Created    11m (x4 over 12m)     kubelet            Created container n8n
  Normal   Started    11m (x4 over 12m)     kubelet            Started container n8n
  Warning  Unhealthy  11m (x8 over 12m)     kubelet            Readiness probe failed: Get "http://10.42.0.10:5678/healthz": dial tcp 10.42.0.10:5678: connect: connection refused
  Warning  BackOff    2m42s (x49 over 12m)  kubelet            Back-off restarting failed container
dolohow commented 1 year ago

Turns out it had problem with connecting to postgres. I had to put rejectUnauthorized: false