Good morning everyone,
since most of my day job is with Helm Charts, I would also like to throw my two pennies in the round.
@sebastian.bezold@xxxxxxxxxxxxxxxxx
I agree with your approach.
To summarize briefly, we need to support two different deployment types:
1. application + chart dependency DB.
2. application + external provided DB.
For the 1st type: I would also just use the secret created by the dependency chart.
For the 2nd type: I like the mechanism that the
bitnami/gitea chart uses. There, in the values.yaml, they introduced a
separate section called "externalDatabase" where they provide the possibility to enter all the needed information like username, password, host, ... .
What I don't like there is that everything except the password must be configured in the values directly. I like the approach of being able to put everything else in
the "existingSecret" secret as well. This allows to have a mechanism or process that automatically provides the database for you and all you have to do is use the secret created (this is perhaps a rather rare use-case for sure).
Since you mentioned JDBC URIs in particular: Depending on the application itself, how it needs to be configured, I would allow users/operators/administrators to decide
for themselves if they want to configure the JDBC URI directly or use the separate configurations. Here I would always use the JDBC URI before the separate configs, because in the most cases it’s more precise than the separate configs.
If the user is given separate configs, you can also build a JDBC URI in the _helpers.tpl if the application needs it.
If you like to create an example or need someone for reviews of helm chart, I always happy to help out!
|
Viele Grüße/Best regards
Florian Rusch
DevSecOps Specialist
|
|
|
|
|
|
cluetec GmbH
Wilhelm-Schickard-Str. 9
76131 Karlsruhe | Deutschland
Telefon:
+49 721 83179-226
Mobile:
+49 160 996 856 80
|
|
|
F.Rusch@xxxxxxxxxx | www.cluetec.de
|
|
|
Geschäftsführer: Matthias Helferich, Thomas Rieger, Hermann Schäfer
Handelsregister: Mannheim HRB 109205, USt-ID-Nr.: DE213118929
|
From:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Paul Latzelsperger via tractusx-dev <tractusx-dev@xxxxxxxxxxx>
Date: Wednesday, 9. August 2023 at 08:06
To: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
Cc: Paul Latzelsperger <paul.latzelsperger@xxxxxxxxxxxxx>
Subject: Re: [tractusx-dev] Helm Charts: Using the auto-generated PosgtreSQL credentials
Achtung: Diese E-Mail stammt von einem externen Absender. Bitte vermeide es, Anhänge oder externe Links zu öffnen
Good morning,
We (Tx-EDC) are using Postgres with multiple JDBC Datasources in our project, and although we may not do exactly what you outlined, I could give a short walkthrough in the upcoming office hours?
On 09.08.2023, at 08:02, sebastian.bezold--- via tractusx-dev <tractusx-dev@xxxxxxxxxxx> wrote:
over time, I got multiple questions on how to handle PostgreSQL credentials and the JDBC (or equivalent for non-Java) connection string in Helm Charts.
Since we do not maintain an application using PostgreSQL in the System Team, I would ask you guys, if you can provide a good example on how this is handled.
What the (imo) best case solution should provide:
-
Picking up the auto-generated credentials from the bitnami postgres dependency, without any configuration needed
-
Automatically configuring the proper connection string, without any configuration needed.
-
Still enable overwriting username and password
-
Enable “external” DB overwrite. -> do not use PostgreSQL as direct Chart dependency, but configure connection and credentials to externally provided service
If anyone already achieved that, I would be great, if you can share a link to the Chart and the template files that contain this config.
Thanks in advance and happy coding
Mit freundlichen Grüßen / Kind regards
Mercedes-Benz Tech Innovation GmbH (ehemals/formerly
Daimler TSS GmbH)
Mercedes-Benz Tech Innovation GmbH
Sitz und Registergericht/Domicile and Register Court: Ulm, HRB-Nr./Commercial Register No.: 3844
Geschäftsführung/Management: Daniel Geisel (Vorsitzender/Chairperson), Isabelle Krautwald
If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.
_______________________________________________
tractusx-dev mailing list
tractusx-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
