MySQL Bugs: #110212: Helm chart cannot use router.podSpec if using tls.useSelfSigned

Bug #110212	Helm chart cannot use router.podSpec if using tls.useSelfSigned
Submitted:	24 Feb 2023 19:15	Modified:	3 Mar 2023 22:04
Reporter:	Thomas Rock	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Operator	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
https://github.com/mysql/mysql-operator/blob/trunk/helm/mysql-innodbcluster/templates/depl...

Values.router.podSpec/podLabels/podAnnotations are used inside the "if not $use_self_signed" conditional which means they cannot be set if using tls.useSelfSigned

The router.podSpec doesn't appear to be related to tls.useSelfSigned, so it shouldn't be inside the conditional.

How to repeat:
When installing/upgrading a mysql-innodbcluster cluster with helm, set tls.useSelfSigned=true and add router.podSpec.* and observe that the router deployment not contain the podSpec you specified.

Suggested fix:
https://github.com/mysql/mysql-operator/blob/trunk/helm/mysql-innodbcluster/templates/depl...

Move the Values.router.podSpec/podLabels/podAnnotations usage after L64 so it's outside of the "if not $use_self_signed" conditional.

Hi,

Thank you for the report

Posted by developer:
 
Fixed as of the upcoming MySQL Operator 8.0.33-2.0.9 release, and here's the proposed changelog entry from the documentation team:

Installing or upgrading a MySQL InnoDBCluster with Helm would ignore a
router.podSpec definition if tls.useSelfSigned was enabled.

Thank you for the detailed bug report.