Hello
Can this be fixed w/o a new release of the operator (by patching a resource) ? If yes, any guidelines ?
If not, any plans to fix that ? … w/o a fix, the operator can NOT be installed on the latest kubernetes version.
Hello
Can this be fixed w/o a new release of the operator (by patching a resource) ? If yes, any guidelines ?
If not, any plans to fix that ? … w/o a fix, the operator can NOT be installed on the latest kubernetes version.
Hey @jamoser ,
hmm, seems it was fixed some time ago (August 2022, version 1.13).
Which version of the Operator are you using?
Thanks a lot.
Ok - that means we have to update to operator v. 1.13 or 1.14
Unanswered | Unsolved | Solved
MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright © 2006 - 2024 Percona LLC. All rights reserved.