-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove MariaDB CRD #173
Remove MariaDB CRD #173
Conversation
bddf2b7
to
9072490
Compare
ce1083b
to
10931a0
Compare
/retest |
OK it looks like there are references to this from both install_yamls as well as openstack-operator, so I can't quite trace out how the build is failing but we would assume the openstack-operator build is somehow failing because things it expects to see have been removed from here. |
To support upstream mariadb-operator removal of the "MariaDB" resource in [1], openstack-operator should refer only to Galera as the relational database deployment [1] openstack-k8s-operators/mariadb-operator#173
To support upstream mariadb-operator removal of the "MariaDB" resource in [1], openstack-operator should refer only to Galera as the relational database deployment [1] openstack-k8s-operators/mariadb-operator#173
10931a0
to
dcd387c
Compare
To support upstream mariadb-operator removal of the "MariaDB" resource in [1], openstack-operator should refer only to Galera as the relational database deployment [1] openstack-k8s-operators/mariadb-operator#173
To support upstream mariadb-operator removal of the "MariaDB" resource in [1], openstack-operator should refer only to Galera as the relational database deployment [1] openstack-k8s-operators/mariadb-operator#173
openstack-k8s-operators now uses Galera exclusively for MySQL/MariaDB access, so the MariaDB CRD can be fully removed.
dcd387c
to
8af0ab9
Compare
/retest |
this should be all set now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if this test helper needs to be change as well:
https://github.com/openstack-k8s-operators/mariadb-operator/blob/4cd7b3f5eedec8fef56396cfb88f3cbd795dbb08/api/test/helpers/crd.go#L103C11-L152
as it refers to the code that looks for MariaDB CR by name
mariadb-operator/api/v1beta1/mariadbdatabase_funcs.go
Lines 79 to 87 in 4cd7b3f
// When the MariaDB CR provides the Service it sets the "cr" label of the | |
// Service to "mariadb-<name of the MariaDB CR>". So we use this label | |
// to select the right Service. See: | |
// https://github.com/openstack-k8s-operators/mariadb-operator/blob/5781b0cf1087d7d28fa285bd5c44689acba92183/pkg/service.go#L17 | |
// https://github.com/openstack-k8s-operators/mariadb-operator/blob/590ffdc5ad86fe653f9cd8a7102bb76dfe2e36d1/pkg/utils.go#L4 | |
selector := map[string]string{ | |
"app": "mariadb", | |
"cr": fmt.Sprintf("mariadb-%s", name), | |
} |
cc @dciabrin does this comment also apply to the Galera CR ? |
I think you are correct. The test helper will need to be updated. But the breakage wouldn't occur until renovate bumps up the mariadb-operator/api dependency right? So we could land this and gradually update the operators to use an equivalent Galera test helper gradually |
still trying to understand the complete flow of this helper, I'm not yet seeing the "breakage" here since this helper seems to be in a closed loop against the local mariadb API in any case (comments are out of date since openstack-k8s-operators/lib-common#352 occurred) but this seems to raise a bigger issue which is that the |
Labeling shouldn't change, the Galera CR and the MariaDB CR both use the same labels so clients looking for the database service don't need to treat MariaDB and Galera separately. Back when this was introduced, the only component that would distinguish those two CR was the MariaDBDatabase controller. |
OK so this is ready |
To support upstream mariadb-operator removal of the "MariaDB" resource in [1], openstack-operator should refer only to Galera as the relational database deployment [1] openstack-k8s-operators/mariadb-operator#173
I've deployed openstack locally using this version of the operator, there's no MariaDB crd in the cluster at all and everything is running fine
|
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
@@ -416,7 +398,7 @@ func (r *MariaDBAccountReconciler) reconcileDelete( | |||
// referenced by the MariaDBDatabase which will lead us to the hostname |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: galera/mariadb is now just galera
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to add this to L397 instead of L398 but github does not allow it
waiting on @dciabrin to /approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dciabrin, gibizer, zzzeek The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6fb96fd
into
openstack-k8s-operators:main
openstack-k8s-operators now uses Galera exclusively for MySQL/MariaDB access, so the MariaDB CRD can be fully removed.