improve aggregated-api-endpoint.md
Signed-off-by: AllenZMC <zhongming.chang@daocloud.io>
This commit is contained in:
parent
67a4d86cb4
commit
abcea6deb1
|
@ -1,6 +1,6 @@
|
|||
# Aggregated Kubernetes API Endpoint
|
||||
|
||||
The newly introduced [karmada-aggregated-apiserver](https://github.com/karmada-io/karmada/blob/master/cmd/aggregated-apiserver/main.go) component aggregates all registered clusters and allows users to access member clusters through Karmada by the proxy endpoint,
|
||||
The newly introduced [karmada-aggregated-apiserver](https://github.com/karmada-io/karmada/blob/master/cmd/aggregated-apiserver/main.go) component aggregates all registered clusters and allows users to access member clusters through Karmada by the proxy endpoint.
|
||||
|
||||
For detailed discussion topic, see [here](https://github.com/karmada-io/karmada/discussions/1077).
|
||||
|
||||
|
@ -74,7 +74,7 @@ Run the below command (replace `{clustername}` with your actual cluster name):
|
|||
kubectl --kubeconfig karmada-apiserver.config get --raw /apis/cluster.karmada.io/v1alpha1/clusters/{clustername}/proxy/api/v1/nodes
|
||||
```
|
||||
|
||||
Or append `/apis/cluster.karmada.io/v1alpha1/clusters/{clustername}/proxy ` to the server address of karmada-apiserver.config, and then you can directly use:
|
||||
Or append `/apis/cluster.karmada.io/v1alpha1/clusters/{clustername}/proxy` to the server address of karmada-apiserver.config, and then you can directly use:
|
||||
|
||||
```shell
|
||||
kubectl --kubeconfig karmada-apiserver.config get node
|
||||
|
@ -98,7 +98,7 @@ Create a serviceaccount that does not have any permission:
|
|||
kubectl --kubeconfig /root/.kube/members.config --context member1 create serviceaccount tom
|
||||
```
|
||||
|
||||
### Step2: Create ServiceAccount in karmada control plane
|
||||
### Step2: Create ServiceAccount in Karmada control plane
|
||||
|
||||
```shell
|
||||
kubectl --kubeconfig /root/.kube/karmada.config --context karmada-apiserver create serviceaccount tom
|
||||
|
@ -188,7 +188,7 @@ Run the command below to access member1 cluster:
|
|||
kubectl --kubeconfig tom.config get --raw /apis/cluster.karmada.io/v1alpha1/clusters/member1/proxy/apis
|
||||
```
|
||||
|
||||
We can found that we were able to access, but run the command below:
|
||||
We can find that we were able to access, but run the command below:
|
||||
|
||||
```shell
|
||||
kubectl --kubeconfig tom.config get --raw /apis/cluster.karmada.io/v1alpha1/clusters/member1/proxy/api/v1/nodes
|
||||
|
@ -247,7 +247,7 @@ kubectl --kubeconfig tom.config get --raw /apis/cluster.karmada.io/v1alpha1/clus
|
|||
|
||||
The access will be successful.
|
||||
|
||||
Or we can append `/apis/cluster.karmada.io/v1alpha1/clusters/member1/proxy ` to the server address of tom.config, and then you can directly use:
|
||||
Or we can append `/apis/cluster.karmada.io/v1alpha1/clusters/member1/proxy` to the server address of tom.config, and then you can directly use:
|
||||
|
||||
```shell
|
||||
kubectl --kubeconfig tom.config get node
|
||||
|
|
Loading…
Reference in New Issue