操作系统信息
vsphere虚拟化,Ubuntu22.04LTS,8C/8G

Kubernetes版本信息

root@sea1-master1:~# kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:46:05Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:38:19Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}

容器运行时

root@sea1-master1:~# crictl version
Version:  0.1.0
RuntimeName:  containerd
RuntimeVersion:  v1.6.19
RuntimeApiVersion:  v1

KubeSphere版本信息
KubeSphere 版本 : v3.3.1

问题是什么
在已有k8s集群上安装kubesphere之后 kubesphere-system 命名空间中的deployment都是单副本。

如果直接设置为3副本 kubectl scale -n kubesphere-system deployment ks-apiserver --replicas 3 ,会导致面板无法登陆(可以访问登陆页面,但是点击登陆按钮之后依旧跳转到登录页)

需要怎样做才能让kubesphere自身实现高可用?

    james-curtis kubesphere自身组件的多副本是根据master节点数来的,你3master节点的kubernetes安装kubesphere,相关组件就是高可用安装

      21 天 后

      qczrzl 感谢您的详细解答。
      但是我发现ks-console只有单副本,如果希望一个master直接断电,但是sphere面板不会出现任何问题,也就是负载均衡到三个ks-console,负载均衡器发现请求超时后再重发请求到其他可用的master,实现0中断。需要怎么做呢