Issue with setup and a Service Account Admin

[rhizoet]

Preflight Checklist

• I could not find a solution in the existing issues, docs, nor discussions
• I have joined the ZITADEL chat

Describe the docs your are missing or that are wrong

As a user we wanted to set up Zitadel with only one service account. Because we want to fill all data only with terraform. However, this does not seem to work because the setup pod says that it is waiting for the container to be terminated. Only unfortunately this never happens until Helm or flux runs into a timeout.

If we take out the appropriate part in the values.yaml that only the service account should be created, the installation works right away.

The MachineKeyPath was not configured, because it was removed in the current version. Unfortunately, this is still in the docs: https://zitadel.com/docs/self-hosting/deploy/kubernetes#setup-zitadel-and-a-service-account-admin.

We use the Helm chart in version 5.0.0 and CockroachDB 11.0.3.

We are now setting up Zitadel with a human user and creating a service account at the beginning so we can use the instance as much as possible with Terraform.

Additional Context

No response

[eliobischof]

Having a service user and a key created should basically work. We add an example for that in PR #111

Is it possible, that flux has problems with the helm hooks? These are defined as defaults in the values.yaml. I think also for ArgoCD they don't work out-of-the box.

[lusu007]

Having a service user and a key created should basically work. We add an example for that in PR #111

Is it possible, that flux has problems with the helm hooks? These are defined as defaults in the values.yaml. I think also for ArgoCD they don't work out-of-the box.

I have successfully installed Zitadel using ArgoCD with only a service account. I didn't encounter any issues during the installation process.

[hifabienne]

I will close this issue for now, as it looks like we have provided some examples, which also work for other customers.
@rhizoet Feel free to reopen if the problem is not solved for you and you can provide more infos