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

Create Documentation for using Postgresql, in addition to (and eventually instead of) Cockroachdb, due to future helm chart deprecation #123

Closed
jessebot opened this issue Aug 19, 2023 · 2 comments

Comments

@jessebot
Copy link
Contributor

jessebot commented Aug 19, 2023

Cockroachdb's helm chart is being deprecated (date unknown currently), see cockroachdb/helm-charts#230 and the docs here.
The CockroachDB Helm chart is compatible with Kubernetes versions 1.22 and earlier. The CockroachDB Helm chart is currently not under active development, and no new features are planned. However, Cockroach Labs remains committed to fully supporting the Helm chart by addressing defects, providing security patches, and addressing breaking changes due to deprecations in Kubernetes APIs. A deprecation notice for the Helm chart will be provided to customers a minimum of 6 months in advance of actual deprecation. Warning: If you are running a secure Helm deployment on Kubernetes 1.22 and later, you must migrate away from using the Kubernetes CA for cluster authentication. For details, see Certificate management https://www.cockroachlabs.com/docs/v23.1/secure-cockroachdb-kubernetes?filters=helm#migration-to-self-signer

It would be nice to see some instructions for Postgresql. I can help with adding a subchart for Bitnami's Postgres helm chart if you'd like. We use it over at the community run Nextcloud helm chart, and it's been pretty smooth sailing so far.

The other issue is that cockroachdb doesn't let you pass in passwords from an existing secret or env var to their init job's provisioning container. See cockroachdb/helm-charts#242 which has not been responded to by anyone from the project in it's year of being open. This means you have to pass in a plain text password if you want to use passwords, which is a non-starter for certain companies and orgs due to security compliance requiring no plain text passwords, even in private repos.

I changed the original title, because it's not yet clear when the helm chart will be deprecated. Cockroachdb also has an Operator which I believe they want you to use instance, but as of now is only tested on GKE and does not have a helm chart at time of writing.

@jessebot jessebot changed the title Create Documentation for using Postgresql instead of Cockroachdb Create Documentation for using Postgresql in addition to Cockroachdb (and eventually instead of) due to future helm chart deprecation. Aug 19, 2023
@jessebot jessebot changed the title Create Documentation for using Postgresql in addition to Cockroachdb (and eventually instead of) due to future helm chart deprecation. Create Documentation for using Postgresql, in addition to (and eventually instead of) Cockroachdb, due to future helm chart deprecation Aug 19, 2023
@eliobischof
Copy link
Member

Does the PR #111 address what you need?

@jessebot
Copy link
Contributor Author

yes, after a quick inspection, thank you! I'll open a new issue if anything doesn't work :)

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

No branches or pull requests

2 participants