-
Notifications
You must be signed in to change notification settings - Fork 29
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
K8SPS-61: Rename CRD to PerconaServerMySQL #45
Conversation
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.
@egegunes please add task number to the PR
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.
In rbac.yaml our roles/rolesbindings are called like:
name: percona-server-for-mysql-operator-leader-election-role
name: percona-server-for-mysql-operator-role
name: percona-server-for-mysql-operator-leader-election-rolebinding
name: percona-server-for-mysql-operator-leader-election-role
name: percona-server-for-mysql-operator-rolebinding
so they have suffix -role
and -rolebinding
which I don't see in PSMDB/PXC operators.
Maybe consider making it the same.
https://github.com/percona/percona-server-mysql-operator/blob/main/deploy/rbac.yaml#L9
https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/rbac.yaml
https://github.com/percona/percona-server-mongodb-operator/blob/main/deploy/rbac.yaml
We're also changing the api version (from v2 to v1alpha1) of our CRD. It may break the new deployments if the old CRDs installed in the cluster. In case of any errors, delete the old ones: ``` kubectl delete crd perconaserverformysqls.ps.percona.com kubectl delete crd perconaserverformysqlbackups.ps.percona.com kubectl delete crd perconaserverformysqlrestores.ps.percona.com ```
commit: 8ab54f7 |
We're also changing the api version (from v2 to v1alpha1) of our CRD. It
may break the new deployments if the old CRDs installed in the cluster.
In case of any errors, delete the old ones: