This is an automated email from the ASF dual-hosted git repository.

zhangjintao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git


The following commit(s) were added to refs/heads/master by this push:
     new 8e3104b3 docs: Add QA about exposing gateway as loadbalancer (#1907)
8e3104b3 is described below

commit 8e3104b3fde9a863a96044e02c34ad63c217f1ae
Author: Ashish Tiwari <[email protected]>
AuthorDate: Tue Aug 1 09:07:14 2023 +0530

    docs: Add QA about exposing gateway as loadbalancer (#1907)
---
 docs/en/latest/FAQ.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/en/latest/FAQ.md b/docs/en/latest/FAQ.md
index 8c01f7b8..39193062 100644
--- a/docs/en/latest/FAQ.md
+++ b/docs/en/latest/FAQ.md
@@ -88,3 +88,18 @@ You can change the Admin API key in two ways:
 
 1. Modify the key in both 
[apisix/values.yaml](https://github.com/apache/apisix-helm-chart/blob/57cdbe461765cd49af2195cc6a1976cc55262e9b/charts/apisix/values.yaml#L181)
 and 
[apisix/apisix-ingress-controller/values.yaml](https://github.com/apache/apisix-helm-chart/blob/57cdbe461765cd49af2195cc6a1976cc55262e9b/charts/apisix-ingress-controller/values.yaml#L128)
 files.
 2. You can also set this imperatively by passing the flag `--set 
ingress-controller.config.apisix.adminKey=<new key> --set 
admin.credentials.admin=<new key>` to the `helm install` command.
+
+## Why does my Ingress resource not have an address?
+
+1. **Using the External address of LoadBalancer service.**
+
+You will need to get the apisix-gateway service an external IP assigned for it 
to reflect on the Ingress's status.
+
+* While installing APISIX helm chart make sure to override gateway type with 
`--set gateway.type=LoadBalancer`.
+
+* Also make sure to pass ingressPublishService while installing Ingress 
controller with `--set 
ingress-controller.config.ingressPublishService=<namespace/service-name>`. If 
namespace is not specified then `default` namespace will be chosen.
+
+Note: External IP is allocated either by cloud provider or some other 
controller like metallb(if you're using kind or minikube) so if you're 
deploying Ingress controller on minikube or kind then make sure to install and 
configure something like metallb with an address pool which can allocate 
external IP for service of type LoadBalancer.
+
+2. **Using the address given explicitly by `ingress_status_address`**
+In case the gateway `service` is not of type LoadBalancer, this field should 
be configured in the config-default.yaml used by the Ingress controller. This 
field takes precedence over ExternalIP of the service so if 
`ingress_status_address` array has non zero elements(addresses) present then it 
will used over the ExternalIP of the gateway service.

Reply via email to