[Architecture] Move from dbaas-controller to dbaas-operator
General
Escalation
General
Escalation
Description
None
How to test
How to document
None
100% Done
relates to
Activity
Show:
Yusaf Awan December 29, 2022 at 1:14 PMEdited
I have logged a bug https://jira.percona.com/browse/PMM-11311, I feel this is a blocker for testing, therefore changing the state to "In Progress". Please let me know if you require any further information.
Andrei Minkin December 26, 2022 at 12:08 PM
Feature build is here https://github.com/Percona-Lab/pmm-submodules/pull/2927
Known issues:
It installs psmdb v1.11 by default, however it is possible to use psmdb v1.12. Sometimes it shows that it's unsupported because of the version service. We can get rid of version service dependency before release.
Expose settings do not apply during the register and should be disabled. We will enable editing these configuration settings later because it's unclear right now.
Basically, we need to do a simple regression testing
Done
Created November 7, 2022 at 9:31 AM
Updated March 6, 2024 at 12:26 AM
Resolved February 27, 2023 at 1:12 PM
A user should perform all operations for database clusters (create, update, upgrade, restart, delete).
During the registering Kubernetes cluster, dbaas-operator should be installed.
There are a lot of failing tests in the dbaas UI tests pipeline https://pmm.cd.percona.com/blue/organizations/jenkins/pmm2-dbaas-e2e-tests/activity because of new changes in the UI