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
Action: add note in documentation to install <=v1.15 for mojaloop <=v8.3.0
Step 4.1 "helm init" may fail with ambiguous message (Error: error installing: Post http://localhost:8080/apis/apps/v1/namespaces/kube-system/deployments: dial tcp 127.0.0.1:8080: connect: connection refused) when .kube/config file is missing.
Action: add note about generating that file.
Pods/services fail to start when one of the needed microk8s plugin is not enabled. Action: add a step to ensure that mandatory services are enabled on microk8s.
Troubleshooting: add a section about looking at output of microk8s.inspect. Example warning about missing "sudo iptables -P FORWARD ACCEPT".
Postman golden path issue found. The default value of HOST_SIMULATOR_K8S_CLUSTER parameter in Mojaloop-Local environment seems to wrong
Summary:
This is list of problems found when strictly following "Local Kubernetes Development Guide" (https://mojaloop.io/documentation/deployment-guide/) with corresponding actions to fix them.
Severity:
Low
Priority:
Low
Expected Behavior
Following the Guide should be straightforward.
Steps to Reproduce
Specifications
Notes:
Details:
Error: error installing: Post http://localhost:8080/apis/apps/v1/namespaces/kube-system/deployments: dial tcp 127.0.0.1:8080: connect: connection refused
) when .kube/config file is missing.Action: add a step to ensure that mandatory services are enabled on microk8s.
microk8s.inspect
. Example warning about missing "sudo iptables -P FORWARD ACCEPT".HOST_SIMULATOR_K8S_CLUSTER
parameter inMojaloop-Local
environment seems to wrongPull Requests:
The text was updated successfully, but these errors were encountered: