congrats on the new release! quick question on Kratos helm deployment. i see folks define the following in

extraInitContainers

in a helm values file:

deployment:      
      extraInitContainers:
        - name: kratos-automigrate
          image: "oryd/kratos:v0.9.0-alpha.3"
          imagePullPolicy: IfNotPresent
          command: ["kratos"]
          args:
            [
              "migrate",
              "sql",
              "-e",
              "--yes",
              "--config",
              "/etc/config/kratos.yaml",
            ]
          volumeMounts:
            - name: kratos-config-volume
              mountPath: /etc/config
              readOnly: true
      ...

if i set

autoMigrate

as

true

do i still need this part? i suppose this specific config and

autoMigrate

will do the same things - creating sql schemas, but here it passes in

--config kratos.yaml

, if i enable

autoMigrate

, it will automatically pick up

kratos.config

defined in the helm values file, no need to define

extraInitContainers

for migration, right?

For reference this was Geoffs answer: I don’t see that. I see a job created with the command as so:

command: ["kratos"]
args: ["migrate", "sql", "-e", "--yes"]

I ran the following then looked at the job.yaml

helm install kratos --set kratos.autoMigrate=true --dry-run ory/kratos | schelm -f output

Although in 0.23.3 I see it as

command: ["kratos"]
args: ["migrate", "sql", "-e", "--yes", "--config", "/etc/config/kratos.yaml"]

thanks for clarifying. i followed up in that thread, it seems config doesn't get picked up https://ory-community.slack.com/archives/C02PSRUGUAV/p1658739421799279?thread_ts=1658383809.718089&cid=C02PSRUGUAV it could be something wrong on my side but i am now trying to figure out