docs: Customize the namespace used for installation (apache#747)

Sindweller · Nov 25, 2021 · 825654c · 825654c
1 parent cead25a
commit 825654c
Show file tree

Hide file tree

Showing 11 changed files with 11 additions and 3 deletions.
diff --git a/docs/en/latest/deployments/ack.md b/docs/en/latest/deployments/ack.md
@@ -45,6 +45,7 @@ helm install apisix apisix/apisix \
   --set etcd.persistence.storageClass="alicloud-disk-ssd" \
   --set etcd.persistence.size="20Gi" \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/aws.md b/docs/en/latest/deployments/aws.md
@@ -43,6 +43,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=LoadBalancer \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/azure.md b/docs/en/latest/deployments/azure.md
@@ -43,6 +43,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=LoadBalancer \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/gke.md b/docs/en/latest/deployments/gke.md
@@ -43,6 +43,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=LoadBalancer \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/k3s-rke.md b/docs/en/latest/deployments/k3s-rke.md
@@ -45,6 +45,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=NodePort \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix \
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
   --kubeconfig /etc/rancher/k3s/k3s.yaml
 kubectl get service --namespace ingress-apisix
 ```

diff --git a/docs/en/latest/deployments/kubesphere.md b/docs/en/latest/deployments/kubesphere.md
@@ -44,6 +44,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=NodePort \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/minikube.md b/docs/en/latest/deployments/minikube.md
@@ -42,6 +42,7 @@ helm install apisix apisix/apisix \
   --set gateway.type=NodePort \
   --set ingress-controller.enabled=true \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/deployments/tke.md b/docs/en/latest/deployments/tke.md
@@ -44,6 +44,7 @@ helm install apisix apisix/apisix \
   --set ingress-controller.enabled=true \
   --set etcd.persistence.size="10Gi" \
   --namespace ingress-apisix
+  --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 kubectl get service --namespace ingress-apisix
 ```
 

diff --git a/docs/en/latest/practices/manage-certificates-with-cert-manager.md b/docs/en/latest/practices/manage-certificates-with-cert-manager.md
@@ -35,7 +35,7 @@ In this guide, we assume that your APISIX is installed with `ssl` enabled, which
 For example, you could install APISIX and APISIX ingress controller by running:
 
 ```bash
-helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true
+helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true --set ingress-controller.config.apisix.serviceNamespace=default
 ```
 
 Assume that the SSL port is `9443`.

diff --git a/docs/en/latest/practices/manage-ingress-certificates-with-cert-manager.md b/docs/en/latest/practices/manage-ingress-certificates-with-cert-manager.md
@@ -35,7 +35,7 @@ In this guide, we assume that your APISIX is installed with `ssl` enabled, which
 For example, you could install APISIX and APISIX ingress controller by running:
 
 ```bash
-helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true
+helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true --set ingress-controller.config.apisix.serviceNamespace=default
 ```
 
 Assume that the SSL port is `9443`.

diff --git a/docs/en/latest/practices/proxy-grpc-service.md b/docs/en/latest/practices/proxy-grpc-service.md
@@ -38,7 +38,7 @@ kubectl create ns ingress-apisix
 You could install APISIX and APISIX ingress controller by running:
 
 ```bash
-helm install apisix apisix/apisix -n ingress-apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true
+helm install apisix apisix/apisix -n ingress-apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --set gateway.tls.enabled=true --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix
 ```
 
 Check that all related components have been installed successfully, including ETCD cluster / APISIX / apisix-ingress-controller.