Add masternode privileges to existing nodes

https://www.kubesphere.io/docs/v3.3/installing-on-linux/cluster-operation/add-new-nodes/

I added a master node to the existing node and ran it, but only a message saying that it was successful came out and the value did not change.
I think the hosts setting is also finished. Anything I need to add?

Below is my sample.yaml

09:56:21 KST Pipeline[AddNodesPipeline] execute successfully
[root@bu20-04 kubernetes]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
bu20-04 Ready control-plane,master 7d22h v1.23.7
bu20-05 Ready worker 7d22h v1.23.7
bu20-06 Ready worker 7d22h v1.23.7

apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
name: sample
spec:
hosts:
- {name: bu20-04, address: 192.168.137.234, internalAddress: 192.168.137.234, user: root, password: "1111"}
- {name: bu20-05, address: 192.168.137.235, internalAddress: 192.168.137.235, user: root, password: "1111"}
- {name: bu20-06, address: 192.168.137.236, internalAddress: 192.168.137.236, user: root, password: "1111"}
roleGroups:
etcd:
- bu20-04
control-plane:
- bu20-04
- bu20-05
worker:
- bu20-05
- bu20-06
controlPlaneEndpoint:
## Internal loadbalancer for apiservers
# internalLoadbalancer: haproxy

domain: lb.kubesphere.local
addres: "192.168.137.13"
port: 6443
kubernetes:
version: v1.23.7
clusterName: cluster.local
autoRenewCerts: true
containerManager: docker
etcd:
type: kubekey
network:
plugin: calico
kubePodsCIDR: 10.233.64.0/18
kubeServiceCIDR: 10.233.0.0/18
## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
multusCNI:
enabled: false
registry:
privateRegistry: ""
namespaceOverride: ""
registryMirrors: []
insecureRegistries: []
addons: []
openpitrix:
store:
enabled: true

Start with the linked add-new-nodes documentation and compare its procedure with the sample.yaml roleGroups and kubectl get nodes output. Reproduce the AddNodesPipeline result if possible, then verify whether the page explains adding control-plane or master roles and whether the observed output indicates a documentation or product issue. Done means the behavior and required configuration are clearly documented or the issue is routed to the appropriate product component.

Written by the indexing model from the issue text.