Mysql can't be in a different namespace than the user/db

[halkeye]

Use Case

1. Have mysql setup in a single namespace (ext-mysql-operator)
2. Have new application in new namespace (new-app)
3. Have MySQLDB in app namespace (new-app)
4. Have mysqluser in app namespace (new-app)

This is to avoid the hostname/password being in each namespace and potentially getting out of sync.

[halkeye]

ideas

1. mysqlDB.Spec.MysqlNamespace

• Have an optional spec field that lets you specify namespace of mysql

2. allow namespace to be specified with /, so
   mysqlDB.Spec.MysqlName = "server" == $namespace/server
   while
   mysqlDB.Spec.MysqlName = "operator/server" == "operator/server" type thing
3. globally search for it across all namespaces if not found
4. Allow hostname/port to be fetched from secret too

[halkeye]

ah, reading the code, the resultant secret doesn't have hostname/port anyways, so i'd have to share it everywhere :(

[nakamasato]

ah, reading the code, the resultant secret doesn't have hostname/port anyways, so i'd have to share it everywhere :(

Do you expect to have db_url in the secret?

[halkeye]

I think so? I've been using https://github.com/movetokube/postgres-operator/ which when you create a postgresuser item, it creates a user and a secret for you. I liked it because my superuser credentials were only in the operator namespace.

[nakamasato]

Let me check it. Thanks.