[Feature]: Connect to OceanBase cluster using okctl

[chris-sun-star]

Describe your use case

okctl is able to read lots of essential information about the managed OceanBase related resources, but for the user it may be hard or complex to get these info, provide this feature will make the users easier to manage OceanBase.

Describe the solution you'd like

provide a simple command to connect to oceanbase cluster using okctl

Describe alternatives you've considered

No response

Additional context

No response

[lizzy-0323]

I am currently implementing this feature, but there is still a point that needs to be discussed.
Currently, do users need to pass in the k8s secret, or directly pass in the password, or is this process directly parsed by okctl? I mean, okctl can get it when the cluster is specified.

[lizzy-0323]

Now I have implemented the function of connecting to the sys tenant through the root user
We can use:

okctl cluster connect <cluster_name> 

to easily connect to a cluster.

And what if we want to connect to a specified tenant? Currently, my idea is to use the following command:

okctl tenant connect <tenant_name> -u=<user> --cluster_name= <cluster_name>

Or we can put these two commands together under the cluster module🤔，but in my opinion, it seems that the main use case for connecting to a cluster is to use sys tenant to connect and view the status or config of the cluster.

Which one is better?

[chris-sun-star]

I think it's better to use a command under tenant, obtenant is a custom resource, so I think it's reasonable to add a command okctl tenant connect.
For the password, it's better to add 2 options for passing secret or the raw password string, maybe you can add an option like -s/--secret, -p/--password. By default, you can use the secret configed in the resource and user root, if the users specify the user option, then they need to pass the password or secret as well.
And there's another question about the command you listed above, are the <cluster_name> and <tenant_name> the custom resource's name or the names in the obcluster, I think it's better to use the custom resource's name, and also add an option to pass the namespace.