karmada-io
/
karmada
mirror of https://github.com/karmada-io/karmada.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #608 from lfbear/pr_append2readme 

Docs: introduce the usage 'CLUSTER_IP_ONLY=true' to the readme
This commit is contained in:
karmada-bot 2021-08-17 09:39:25 +08:00 committed by GitHub
parent 67ded1f9ed d3ac8ea545
commit d76e206c97
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -160,7 +160,7 @@ There are two contexts you can switch after the script run are:
The `karmada-apiserver` is the **main kubeconfig** to be used when interacting with karamda control plane, while `karmada-host` is only used for debugging karmada installation with host cluster, you can check all clusters at any time by run: `kubectl config view` and switch by `kubectl config use-context [CONTEXT_NAME]` The `karmada-apiserver` is the **main kubeconfig** to be used when interacting with karamda control plane, while `karmada-host` is only used for debugging karmada installation with host cluster, you can check all clusters at any time by run: `kubectl config view` and switch by `kubectl config use-context [CONTEXT_NAME]`
##### 3.2. I have present cluster for installing ##### 3.2. I have present cluster for installing
Before running the following script, please make sure your cluster could provide `LoadBalancer` type service. Before running the following script, please make sure your cluster could provide the `LoadBalancer` type service. Otherwise, type `export CLUSTER_IP_ONLY=true` with the `ClusterIP` type service before the following script.
``` ```
# hack/remote-up-karmada.sh <kubeconfig> <context_name> # hack/remote-up-karmada.sh <kubeconfig> <context_name>
``` ```