[Bug] Remove old dependency to sigs.k8s.io/controller-runtime and sigs.k8s.io/controller-runtime/pkg/envtest/printer about mariadb-operator

[mmontes11]

Hey there @mhuin ! Thanks for bringing this up

I think it makes sense to upgrade to ginkgo v2, actually, it is in our radar:

• #3

We will tackle this in the next release 👍🏻

Out of curiosity, what is your use case for consuming mariadb-operator as a package?

[mhuin]

Out of curiosity, what is your use case for consuming mariadb-operator as a package?

My team is writing an operator for the Software Factory project ( https://www.softwarefactory-project.io ), mariadb is a dependency for some of our services. Being new to operator development, we were experimenting with deploying mariadb programmatically in our controller via the operator. In the end we chose to keep things simple by using a simple deployment of a mariadb container; we just kept the database connection secret's structure from the mariadb operator in case we opt to use it later. The package was used to compute the DSN; it was trivial to drop that dependency but I thought you might want to know about this issue.

[mmontes11]

Thanks for the context @mhuin !

The package was used to compute the DSN;

That makes sense, packages are there to be reused 👍🏻

it was trivial to drop that dependency but I thought you might want to know about this issue.

Yes indeed, thanks for letting me know, I'm aiming to bump to the latest controller-runtime and ginkgo versions in this release.

we were experimenting with deploying mariadb programmatically in our controller via the operator. In the end we chose to keep things simple by using a simple deployment of a mariadb container

Happy to provide some guidance in case you decide to finally use the operator. Just open another issue or drop a message in our slack channel

[github-actions]

This issue is stale because it has been open 30 days with no activity.