MySQL Bugs: #108717: MySQL Operator - documentation installing using kubectl fails

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:	None
Category:	MySQL Operator	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
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.

Hi,

Thanks for the report

Posted by developer:
 
I can't reproduce this and do see both mycluster and mycluster-instances:

$ kubectl get services

kubernetes            ClusterIP   10.96.0.1        <none>        443/TCP                                                  16m
mycluster             ClusterIP   10.103.113.230   <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.

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".

Posted by developer:
 
Closing without a release note; we suspect it was a temporary error.