search

wso2 / kubernetes-apim

Kubernetes and Helm resources for WSO2 API Manager
Apache License 2.0
112 stars 216 forks source link

APIM deployment failed on Rancher Desktop #563

Open LahiruSammika95 opened 1 year ago

LahiruSammika95 commented 1 year ago

Description

I tried APIM with both Docker Desktop and Rancher Desktop. When using Docker Desktop, APIM deployed successfully. However, with Rancher Desktop, Mysql Pod remained in the init state.

Affected Product Version

  1. WSO2 APIM 4.1.0
  2. Rancher Desktop 1.5.1

Steps to reproduce

  1. Spin up a cluster using Rancher Desktop
  2. Disable Traefik ingress controller and install NGINX ingress controller
  3. Deploy WSO2 APIM 4.1.0 on Rancher Desktop

WSO2 APIM error stacktrace

The following error message appeared after running the kubectl describe command on the mysql pod.

Mounting arguments: -t nfs -o vers=3 10.43.208.49:/export/pvc-f7393941-bcaf-4d7a-aee4-c7e572ab2f84 /var/lib/kubelet/pods/13600e2d-578e-4e52-844a-6b55f34d66e7/volumes/kubernetes.io~nfs/pvc-f7393941-bcaf-4d7a-aee4-c7e572ab2f84 Output: mount: mounting 10.43.208.49:/export/pvc-f7393941-bcaf-4d7a-aee4-c7e572ab2f84 on /var/lib/kubelet/pods/13600e2d-578e-4e52-844a-6b55f34d66e7/volumes/kubernetes.io~nfs/pvc-f7393941-bcaf-4d7a-aee4-c7e572ab2f84 failed: Connection refused Warning FailedMount 6s (x2 over 9m10s) kubelet Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[migrations data kube-api-access-bfg6l configurations]: timed out waiting for the condition

Capture7 Capture4 (2)
LahiruSammika95 commented 1 year ago

I was able to successfully deploy APIM on Rancher Desktop after replacing the "nfs" storage class with the "local-path" storage class in the values.yaml. But I'm not sure this is the best course of action.

Capture5 Capture6 Capture8