You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: deployment-guide/deployment-troubleshooting.md
+30
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@
5
5
### 1.1. `ERR_NAME_NOT_RESOLVED` Error
6
6
7
7
#### Description
8
+
8
9
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`
9
10
10
11
#### Fixes
@@ -20,3 +21,32 @@ The following error is displayed when attempting to access an end-point (e.g. ce
20
21
* Ensure that all the Mojaloop Pods/Containers have started up correctly and are available through the Kubernetes dashboard.
21
22
22
23
* 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.
24
+
25
+
### 1.2. Ingress rules are not resolving for Nginx Ingress v0.22 or later
26
+
27
+
#### Description
28
+
29
+
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.
30
+
31
+
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.
32
+
33
+
#### Fixes
34
+
35
+
* Make the following change to all Ingress annotations (from --> to) in each of the values.yaml files:
### 1.3. Ingress rules are not resolving for Nginx Ingress earlier than v0.22
41
+
42
+
#### Description
43
+
44
+
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.
45
+
46
+
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.
47
+
48
+
#### Fixes
49
+
50
+
* Make the following change to all Ingress annotations (from --> to) in each of the values.yaml files:
0 commit comments