docs icon indicating copy to clipboard operation
docs copied to clipboard

Inconsistent best practices regarding the Database - Kubernetes interconnection

Open sebastian-philipp opened this issue 1 year ago • 0 comments

Hi there,

In https://docs.ovh.com/de/publiccloud/databases/mysql/tutorial-connect-kubernetes-to-managed-mysql/#step-5-configure-your-options , you're recommending using a public network for the interconnection between Mysql and the Kubernetes cluster.

But In Discord, Bastien Verdebout mentioned:

Hello Sebastian Wagner indeed so far you need to select a private network option during DB creation. you cannot modify it once the clsuter is running. About best practices, having a private network will allow you to secure a bit more your infra, and benefit from more bandwidth. but you will need a gateway to connect to your DB (for example you cannot do laptop (postgre CLI ==> DB). you will need a vm inside you vrack with postgre CLI. that's not worse, it' in fact better since you can log this machine like a bastion, but it's something to know)

So, you should probably decide on a best practice.

https://docs.ovh.com/gb/en/kubernetes/vrack-k8s-custom-gateway/ also gave me some insights.

sebastian-philipp avatar Aug 09 '22 14:08 sebastian-philipp