Bug #108717 MySQL Operator - documentation installing using kubectl fails
Submitted: 9 Oct 2022 13:39 Modified: 10 Jan 2023 23:06
Reporter: Simon Schöning Email Updates:
Status: Closed Impact on me:
Category:MySQL Operator Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[9 Oct 2022 13:39] Simon Schöning
Following the tutorial on installing via kubectl manifests
"https://dev.mysql.com/doc/mysql-operator/en/mysql-operator-innodbcluster-simple-kubectl.ht...", the last command 
"kubectl run --rm -it myshell --image=mysql/mysql-operator -- mysqlsh root@mycluster --sql"
fails. During the tutorial there is no service "mycluster" created, but a service "mycluster-instances". 

How to repeat:
Follow the instructions for installing with kubectl as in the documentation: "https://dev.mysql.com/doc/mysql-operator/en/mysql-operator-installation-kubectl.html". Try to run the last command, documented at: "https://dev.mysql.com/doc/mysql-operator/en/mysql-operator-innodbcluster-simple-kubectl.ht..."

Suggested fix:
Rename the non existing service "mycluster" in the kubectl command to "mycluster-instance" or create a "mycluster" service.
[17 Oct 2022 20:19] MySQL Verification Team

Thanks for the report
[8 Dec 2022 21:30] Philip Olson
Posted by developer:
I can't reproduce this and do see both mycluster and mycluster-instances:

$ kubectl get services

kubernetes            ClusterIP        <none>        443/TCP                                                  16m
mycluster             ClusterIP   <none>        3306/TCP,33060/TCP,6446/TCP,6448/TCP,6447/TCP,6449/TCP   13m
mycluster-instances   ClusterIP   None             <none>        3306/TCP,33060/TCP,33061/TCP                             13m

Connecting to either via shell works. Please reconfirm what you are seeing.
[9 Jan 2023 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[10 Jan 2023 23:06] Philip Olson
Posted by developer:
Closing without a release note; we suspect it was a temporary error.