Remove Cockroach Support

[hifabienne]

Cockroachdb is not postgresql compliant and engineering overhead is too high (writing custom code, custom workaround for using libraries like river). With their newly introduced pricing customers might switch to postgres anyway

Timeline

Starting with Zitadel Version 3, we will exclusively support PostgreSQL, discontinuing support for CockroachDB. Consequently, following our Quarterly Release Strategy, Zitadel Version 2, the last version with CockroachDB support, will reach its end-of-support on September 30, 2025."

Migration

The following migration guide outlines the steps for migrating between databases, including CockroachDB to PostgreSQL.

https://zitadel.com/docs/self-hosting/manage/cli/mirror We will provide more detailed instructions specific to the CockroachDB to PostgreSQL migration in our documentation following the release of Zitadel Version 3.

TODOs:

• ensure mirror command works properly (fix(cmd): ensure proper working of mirror #9509)
• ensure docs for mirror are up to date (fix(cmd): ensure proper working of mirror #9509)
• remove cockroachdb code from Zitadel (chore!: remove CockroachDB Support #9444)
• error handling if cockroach is configured as database (chore!: remove CockroachDB Support #9444)
• Add note on all cockroach docs that this is only support in version 2 (docs: deprecation of Cockroachdb #9480)
• Ensure all docs clearly state that postgreSQL is the recommended db, and per default we show those docs in guides etc. (docs: deprecation of Cockroachdb #9480)
• charts docs (update docs to use postgres zitadel-charts#322)
• knative example (update docs to use postgres zitadel-charts#322)
• helm docs (update docs to use postgres zitadel-charts#322)

[adlerhurst]

missed the charts repo, it currently defaults to cockroachdb which must not be possible for v3.