[k8s operator] Allow every field from Credentials to be configured from a secret

[eshepelyuk]

Hi all

It would be useful to to extend credentials field to allow at least host and user to be picked up from a secret. Ideally every field could be picked up from the secret.

https://atlasgo.io/integrations/kubernetes/operator#credentials-object

The motivation is that we're using 3rd party software (Crossplane) to create DB and role for a microservices. As a result the k8s secret is generated with username, db host, port and password. Unfortunately Crossplane 's secret structure is static. Also the db host / username can vary depending on Crossplane CRD config, so they can't be hardcoded in advance in Atlas CRD.
Currently as a workaround I have to generate another Atlas specific secret that contains URL from the secret created by Crossplane .

For the same purpose I also would like to have a new field of the same credentials type to be introduced for using it as a devDB credentials.

Crossplane secret for pgsql contains

• username
• password
• endpoint (aka host)
• port

[datdao]

Hi @eshepelyuk, thanks for your request, and it seems reasonable to pick the username and host from the secret. You will have it in the next release.

[eshepelyuk]

Hi @eshepelyuk, thanks for your request, and it seems reasonable to pick the username and host from the secret. You will have it in the next release.

Thanks for quick feedback,
Does it also mean that devCredentials will be introduced to allow referring devDB credentials by using Crossplane secret ?

[datdao]

Does it also mean that devCredentials will be introduced to allow referring devDB credentials by using Crossplane secret ?

Hi @eshepelyuk, We will consider adding devCredentials. However, the operator already handles spinning up devDB for you and cleanup as well. So, may I ask if there is any special case where you need to use a custom devDB?

[eshepelyuk]

Does it also mean that devCredentials will be introduced to allow referring devDB credentials by using Crossplane secret ?

Hi @eshepelyuk, We will consider adding devCredentials. However, the operator already handles spinning up devDB for you and cleanup as well. So, may I ask if there is any special case where you need to use a custom devDB?

https://discord.com/channels/930720389120794674/1147429172076097647

[datdao]

Hi @eshepelyuk, we have released Operator v0.3.3 🎉 with more flexibility when configuring credentials #90. According to this update, we have also added a new flag prewarmDevDB to control the lifecycle of devDB. You can configure the flag as false if you want the devDB pod to be deleted entirely after the migration process. Here's an example of how to configure the flag during chart installation

helm install atlas-operator oci://ghcr.io/ariga/charts/atlas-operator --create-namespace --namespace atlas-operator --set prewarmDevDB=false

Thanks for your contribution ❤️ . I will mark the issue as resolved. Feel free to create new issues if you have any ideas for improvements.

[ievgenii-shepeliuk]

Thanks will give it a try hopefully this week.