28 length issue

[johnnyrun]

Issuing commands "as is" I hitted this problem:

E0716 08:16:40.581483       1 controller.go:289] error syncing 'yaxxxay/example-mysql-cluster-with-volume': validating Cluster: metadata.name: Invalid value: "example-mysql-cluster-with-volume": longer than maxi
mum supported length 28 (see: https://bugs.mysql.com/bug.php?id=90601)       

s/example-// fixed.

Thanks

[owainlewis]

Thanks @johnnyrun. Would you mind signing the Oracle Contributor Agreement (CLA) and signing-off your commit so we can merge (see: CONTRIBUTING.md for details)?

The CLA can be found here https://www.oracle.com/technetwork/community/oca-486395.html

If you're comfortable doing that, let us know when it's submitted and we can merge your changes.

Let us know if you have any questions.

[johnnyrun]

@owainlewis cla sent

[owainlewis]

@johnnyrun great thanks. I'll chase up tomorrow and I'll merge when approved internally. 👍

[jascott1]

@owainlewis What is the reason for the 28 char limit? Thanks!

[prydie]

@jascott1 InnoDB clustering only supports cluster members connecting to one another on DNS names of a certain length (defined by the hostname RFC). The MySQL Operator configures the MySQL instances to communicate using name-<ordinal>.name (e.g. my-cluster-0.my-cluster) hence the short name requirement.