Drasi API not available

[aravind-venkedeshwaran]

Steps to reproduce

I encountered timeout issues during installation while following the Drasi getting-started guide. When attempting to create a source using drasi apply -f ./resources/hello-world-source.yaml, I received the error: Error: drasi API not available. The timeouts occur during the Drasi installation process. But drasi seems to works but Drasi-API is the issue.

Observed behavior

Desired behavior

Expected: Create all the deployments mentioned in the guide and explore drasi

Workaround

No response

Drasi Version

Drasi CLI version: 0.1.4

Operating system

Linux d78b2c86c314 6.1.61-85.141.amzn2023.aarch64 #1 SMP Wed Nov 8 00:38:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Additional context

No response

Would you like to support us?

• [X] Yes, I would like to support you

[NValsan]

Thank you for filing this issue. We will look into this and share our findings. If there is any additional info you'd like to share about the issue, please do let us know.

[ruokun-niu]

Hi @aravind-venkedeshwaran, thank you for filing the issue. I suspect that something went wrong during the install. Can you try running kubectl get pods -n drasi-system to check the status of the pods?

[aravind-venkedeshwaran]

kubectl get pods -n drasi-system

Event of drasi-resource-provider-7dcd95db5c-tv99f pod

Event of otel-collector-8c7496f88-hrd2g pod

[aravind-venkedeshwaran]

I manually installed docker pull ghcr.io/drasi-project/kubernetes-provider:0.1.3 and restart the pods again And got this error Liveness probe failed: HTTP probe failed with statuscode: 500 and Readiness probe failed: HTTP probe failed with statuscode: 500

[aravind-venkedeshwaran]

Seems like kubernetes-provider:0.1.3 Doesn't fit for my machine

[ruokun-niu]

Hi @aravind-venkedeshwaran, thanks for providing the screenshots. Seems like this is due to an image architecture issue.

Our 0.1.3 images were actually not multi-arch images. However, we recently did a new release (0.1.5) where all of the images are built as multi-arch images. This should solve the issue.

I'd recommend re-installing the Drasi CLI using the installation script and re-deploying the newest version of Drasi in a new Kubernetes cluster.

[aravind-venkedeshwaran]

Thanks @ruokun-niu 👍

[ruokun-niu]

Hi @aravind-venkedeshwaran, just a heads up that I am closing this issue. Feel free to open it again if there are any new issues :)