Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi all :wave:  When I deploy the kratos helm release version `v0.23.3` (latest release), the automigrate job finishes successfully, but it does not create the `kratos-[id]` and `kratos-courier` pods. The status of the automigrate pod is `NotReady`, but describing it shows that it's ready:
```$ kubectl describe pod kratos-automigrate-t8n4h
  kratos-automigrate:
...
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 15 Jul 2022 15:45:14 +0200
      Finished:     Fri, 15 Jul 2022 15:45:51 +0200
    Ready:          False
    Restart Count:  0```
Describing the job shows:
```$ kubectl describe job kratos-automigrate
...
Parallelism:    1
Completions:    1
Start Time:     Fri, 15 Jul 2022 15:45:10 +0200
Pods Statuses:  1 Active / 0 Succeeded / 0 Failed```
Which makes sense, since the pod remains active to allow inspection of its status, logs, etc.

Logs show successful migrations:
```$ kubectl logs kratos-automigrate-t8n4h kratos-automigrate
...
Successfully applied SQL migrations!```
Why aren't the other pods start up - `kratos` and `kratos-courierr` - that make up the deployment, if all seems well concerning the migrations?

Config is basically the docs with `kratos.automigrate` set to `true`. Plus a dsn set to a postgres server.