From 4c55cae247dedbdc8c17a1683ba0b854b750c9dc Mon Sep 17 00:00:00 2001 From: Miguel de Barros Date: Mon, 10 Jun 2019 13:13:51 +0100 Subject: [PATCH] Added FAQ for ingress issue (#69) * Added FAQ for ingress issue - story https://github.com/mojaloop/helm/issues/196 --- .../deployment-troubleshooting.md | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/deployment-guide/deployment-troubleshooting.md b/deployment-guide/deployment-troubleshooting.md index 052f59064..e81baf717 100644 --- a/deployment-guide/deployment-troubleshooting.md +++ b/deployment-guide/deployment-troubleshooting.md @@ -5,6 +5,7 @@ ### 1.1. `ERR_NAME_NOT_RESOLVED` Error #### Description + The following error is displayed when attempting to access an end-point (e.g. central-ledger.local) via the Kubernetes Service directly in a browser: `ERR_NAME_NOT_RESOLVED` #### Fixes @@ -20,3 +21,35 @@ The following error is displayed when attempting to access an end-point (e.g. ce * Ensure that all the Mojaloop Pods/Containers have started up correctly and are available through the Kubernetes dashboard. * Note that the Mojaloop deployment via Helm can take a few minutes to initially startup depending on the system's available resources and specification. It is recommended that you wait at least 10m for all Pods/Containers to self heal before troubleshooting. + + +## 2. Ingress issues + +### 2.1. Ingress rules are not resolving for Nginx Ingress v0.22 or later + +#### Description + +Ingress rules are unable to resolve to the correct path based on the annotations specified in the values.yaml configuration files when using Nginx Ingress controllers v0.22 or later. + +This is due to the changes introduced in Nginx Ingress controllers that are v0.22 or later as per the following link: https://kubernetes.github.io/ingress-nginx/examples/rewrite/#rewrite-target. + +#### Fixes + + * Make the following change to all Ingress annotations (from --> to) in each of the values.yaml files: + + `nginx.ingress.kubernetes.io/rewrite-target: '/'` --> `nginx.ingress.kubernetes.io/rewrite-target: '/$1'` + + +### 2.2. Ingress rules are not resolving for Nginx Ingress earlier than v0.22 + +#### Description + +Ingress rules are unable to resolve to the correct path based on the annotations specified in the values.yaml configuration files when using Nginx Ingress controllers that are older than v0.22. + +This is due to the changes introduced in Nginx Ingress controllers that are v0.22 or later as per the following link: https://kubernetes.github.io/ingress-nginx/examples/rewrite/#rewrite-target. + +#### Fixes + + * Make the following change to all Ingress annotations (from --> to) in each of the values.yaml files: + + `nginx.ingress.kubernetes.io/rewrite-target: '/$1'` --> `nginx.ingress.kubernetes.io/rewrite-target: '/'`