Merge pull request #1414 from XiShanYongYe-Chang/update-mci-doc

[docs] Correct the syntax errors in the mci document
This commit is contained in:
karmada-bot 2022-03-01 10:13:17 +08:00 committed by GitHub
commit 5cc7da3918
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions

View File

@ -34,7 +34,7 @@ git clone git@github.com:karmada-io/multi-cluster-ingress-nginx.git
#### Build and deploy ingress-nginx
Using existing `karmada-host` kind cluster to building and deploying the ingress controller.
Using the existing `karmada-host` kind cluster to build and deploy the ingress controller.
```
export KIND_CLUSTER_NAME=karmada-host
@ -50,7 +50,7 @@ Create a secret that contains the `karmada-apiserver` authentication credential
# karmada-kubeconfig-secret.yaml
apiVersion: v1
data:
kubeconfig: {data} # encoded by base64
kubeconfig: {data} # Base64-encoded
kind: Secret
metadata:
name: kubeconfig
@ -72,7 +72,7 @@ kubectl apply -f karmada-kubeconfig-secret.yaml
#### Edit ingress-nginx-controller deployment
We want `nginx-ingress-controller` to access `karmada-apiserver` to listen to resource(such as multiclusteringress, endpointslices, service, etc.) changes, therefore, we need to mount the authentication credential of `karmada-apiserver` to the `nginx-ingress-controller`.
We want `nginx-ingress-controller` to access `karmada-apiserver` to listen to changes in resources(such as multiclusteringress, endpointslices, and service). Therefore, we need to mount the authentication credential of `karmada-apiserver` to the `nginx-ingress-controller`.
```
kubectl -n ingress-nginx edit deployment ingress-nginx-controller
@ -106,7 +106,7 @@ spec:
secretName: kubeconfig # new line
```
### Step 2: Use MCS feature to discovery service
### Step 2: Use the MCS feature to discovery service
#### Install ServiceExport and ServiceImport CRDs