From dd3252cf77c854b1bd0bb2d35b160e69150ba08d Mon Sep 17 00:00:00 2001 From: Miguel de Barros Date: Mon, 10 Jun 2019 12:07:05 +0100 Subject: [PATCH 1/2] Added FAQ for ingress issue story https://github.com/mojaloop/helm/issues/196 --- .../deployment-troubleshooting.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/deployment-guide/deployment-troubleshooting.md b/deployment-guide/deployment-troubleshooting.md index 052f59064..6ca7f3aff 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,32 @@ 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. + +### 1.2. 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'` + + +### 1.3. 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: '/'` From 2d3e4f860b8a3df7a779678fe82829704b260f0f Mon Sep 17 00:00:00 2001 From: Miguel de Barros Date: Mon, 10 Jun 2019 12:10:31 +0100 Subject: [PATCH 2/2] updated FAQ to include ingress issue section --- deployment-guide/deployment-troubleshooting.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/deployment-guide/deployment-troubleshooting.md b/deployment-guide/deployment-troubleshooting.md index 6ca7f3aff..e81baf717 100644 --- a/deployment-guide/deployment-troubleshooting.md +++ b/deployment-guide/deployment-troubleshooting.md @@ -22,7 +22,10 @@ The following error is displayed when attempting to access an end-point (e.g. ce * 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. -### 1.2. Ingress rules are not resolving for Nginx Ingress v0.22 or later + +## 2. Ingress issues + +### 2.1. Ingress rules are not resolving for Nginx Ingress v0.22 or later #### Description @@ -37,7 +40,7 @@ This is due to the changes introduced in Nginx Ingress controllers that are v0.2 `nginx.ingress.kubernetes.io/rewrite-target: '/'` --> `nginx.ingress.kubernetes.io/rewrite-target: '/$1'` -### 1.3. Ingress rules are not resolving for Nginx Ingress earlier than v0.22 +### 2.2. Ingress rules are not resolving for Nginx Ingress earlier than v0.22 #### Description