Bug #108581 Mysqlrouter configuration bind_address ipv6 with mysqlcluster operator
Submitted: 22 Sep 2022 16:33 Modified: 22 Sep 2022 22:55
Reporter: Miguel Murillo Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Operator Severity:S2 (Serious)
Version:8.0.29 OS:Other (docker image)
Assigned to: CPU Architecture:Any

[22 Sep 2022 16:33] Miguel Murillo
Description:
Mysqlrouter fails on ipv6 pure environment deployed on k8s.

the reason seems it is bind to ipv4 address 0.0.0.0 when it is created by mysql-operator.

MySQL operator creates the deployment with variable:
MYSQL_ROUTER_BOOTSTRAP_EXTRA_OPTIONS
but it is not configurable to add bind_address=::/0 with helm charts.

How to repeat:
Deploy mysqlrouter on IPV6 pure env.

Suggested fix:

make configurable on helm chart deploy "values.yaml" the option to add variables to MYSQL_ROUTER_BOOTSTRAP_EXTRA_OPTIONS.

Workaround:
modify manually deployment created by mysqloperator adding the option on MYSQL_ROUTER_BOOTSTRAP_EXTRA_OPTIONS.
[22 Sep 2022 22:54] MySQL Verification Team
Hi,

Thank you for the report

all best