Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment stuck, pod is unhealthy #493

Open
tadjik1 opened this issue Jan 15, 2024 · 1 comment
Open

Deployment stuck, pod is unhealthy #493

tadjik1 opened this issue Jan 15, 2024 · 1 comment
Assignees

Comments

@tadjik1
Copy link

tadjik1 commented Jan 15, 2024

Chart Name

bookstack

Chart Version

0.14.0

Problem

I'm using the default configuration (except for the ingress), and I see in logs that pod starts successfully. But it doesn't pass healthy check. I'm out of ideas what needs to be changed (since there is underlying dependency chart that creates services and deployments it's rather difficult to debug the problem. Maybe someone already faced this problem?

values.yaml

bookstack:
  ingress:
    main:
      enabled: true
      className: nginx
      annotations:
        kubernetes.io/tls-acme: "true"
        cert-manager.io/cluster-issuer: letsencrypt-prod
        external-dns-enabled: ""
        external-dns.alpha.kubernetes.io/access: public
        nginx.ingress.kubernetes.io/auth-url: "https://auth.xxxxx/oauth2/auth"
        nginx.ingress.kubernetes.io/auth-signin: "https://auth.xxxxx/oauth2/start?rd=https%3A%2F%2F$host$request_uri"
        nginx.ingress.kubernetes.io/enable-access-log: "false"
      hosts:
        - host: xxxx
          paths:
            - path: /
              pathType: ImplementationSpecific
      tls:
        - secretName: bookstack-certificate
          hosts:
            - xxxx

  service:
    main:
      ports:
        http:
          port: 8080

  mariadb:
    enabled: true
    primary:
      persistence:
        enabled: true

Relevant log output

in bookstack pod:

Waiting for DB to be available   INFO  Nothing to migrate.[custom-init] No custom files found, skipping...[ls.io-init] done.

k8s logs:

Startup probe failed: dial tcp 10.36.11.118:8080: connect: connection refused
@gabe565
Copy link
Owner

gabe565 commented Jan 15, 2024

@tadjik1 Try to remove the bookstack: on line 1 of your values.yaml. MariaDB isn't enabled by default, and the chart expects those values to be in the root, so I believe it isn't deploying the database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants