You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes we need multiple environments for development and testing purposes. It's hard to memorize the address of those KubeSphere clusters. Even worse, part of those environments might be temporary. Give that, it would be good to have a simple way to set up a remote kubeclt connection locally, open the console of the KubeSphere cluster.
You can consider the following usage:
ks config add --cluster dev --host 192.168.0.3
The above command will get the token of the default serviceAccount, then add it to ~/.kube/config as dev. Secondly, create a configMap to store the address of the cluster. It could be like:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.
case 1
Sometimes we need multiple environments for development and testing purposes. It's hard to memorize the address of those KubeSphere clusters. Even worse, part of those environments might be temporary. Give that, it would be good to have a simple way to set up a remote
kubeclt
connection locally, open the console of the KubeSphere cluster.You can consider the following usage:
ks config add --cluster dev --host 192.168.0.3
The above command will get the token of the default serviceAccount, then add it to
~/.kube/config
asdev
. Secondly, create a configMap to store the address of the cluster. It could be like:If you want to open it in your browser, just need to type:
ks open dev
.The text was updated successfully, but these errors were encountered: