Bug #108082 Contribution: Customize Edition
Submitted: 5 Aug 2022 18:02 Modified: 8 Aug 2022 4:48
Reporter: OCA Admin (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Operator Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[5 Aug 2022 18:02] OCA Admin
Description:
This bug tracks a contribution by Alberto Clemente (Github user: Albe83) as described in http://github.com/mysql/mysql-operator/pull/17

How to repeat:
See description

Suggested fix:
See contribution code attached
[5 Aug 2022 18:02] OCA Admin
Contribution submitted via Github - Customize Edition 
(*) Contribution by Alberto Clemente (Github Albe83, mysql-operator/pull/17#issuecomment-1206656184): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_1018764573.txt (text/plain), 1.07 KiB.

[8 Aug 2022 4:48] MySQL Verification Team
Hello Alberto Clemente,

Thank you for the report and contribution.

regards,
Umesh
[10 Aug 2022 15:12] Johannes Schl├╝ter
Posted by developer:
 
Setting the edition for each individual InnoDB Cluster is a functionality to use for our testing as the Operator code is the same between editions.

Enterprise users are required to run the full stack using enterprise edition by using enterprise charts from MyOracle Support (which installs an Enterprise Operator, which install Enterprise MySQL Server) to be covered. Community users don't have access to enterprise Server. Thus setting this per InoDB Cluster is not supported and will not be supported.

We however can look if we can use community helm charts to install Enterprise operator for customers, which then would install enterprise InnoDB Cluster. Keeping the report open for that, while we won't merge the patch as it is.
[1 Sep 2022 19:49] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Operator 8.0.30-2.0.6 release, and here's the proposed changelog entry from the documentation team:

For Helm, added support to select the MySQL Edition (as either 'community' or 'enterprise'). 

Our thanks to Alberto Clemente for the contribution.

Thank you for the bug report.