Add compatibility with public managed db and improve chart

[ccleouf66]

Hey,

I add a logic to detect if the MDB is deployed in public or private mode and based on that the operator is able to select public or private ip of node. If the Kubernetes cluster is configured to use a GW as egress instead using public ip of each node, the operator detect the public ip address used by this GW with https://ifconfig.io.

I also made some change on the chart:

• use helm release ns instead of ns specified in values (helm install ovh-db-operator -n ovh-db-operator --create-namespace .)
• remove unnecessary roles
• add ability to use an existing secret

[apinter]

Could someone from OVH take a look at this? I'm in the process of sorting this for us in a different way, but having an upstream solution from OVH would be a good idea. Ping @BellionBastien

[BellionBastien]

Hello @apinter, I've already started taking a look at it. I wil try to finish my review this week :)

[apinter]

Hello @apinter, I've already started taking a look at it. I wil try to finish my review this week :)

Not to sounds pushy, but happened to make any progress on this? If its going to be dropped or if it takes longer I will need to go back to our in-house solution, but that is currently in the backlog since we're waiting for an upstream solution.

[BellionBastien]

Hello @apinter, no worries, it's understandable :)

You can expect a new release with this included today or tomorrow ;)

[BellionBastien]

@apinter the new release is now available: https://hub.docker.com/r/ovhcom/public-cloud-databases-operator/tags

Helm chat version 0.1.3 and docker image v1.0.3

[apinter]

@apinter the new release is now available: https://hub.docker.com/r/ovhcom/public-cloud-databases-operator/tags

Helm chat version 0.1.3 and docker image v1.0.3

Big thanks @BellionBastien, testing it in a bit ;)

[apinter]

Works great, thank you @ccleouf66 @BellionBastien