Arangodb not getting deployed on AWS EKS cluster though worked on local K8s cluster about arangodb HOT 8 CLOSED

Hi,
currently supported ArangoDB versions include: 3.10.x, 3.11.x ; Somehow the versions you mention completely won't match this scheme?

from arangodb.

@dothebart I was actually referring to kube-arangodb manifest version : https://github.com/arangodb/kube-arangodb/releases/tag/1.2.37 Let me edit.
Which uses the latest arangodb image for ArangoDeployment.

from arangodb.

@dothebart we tried with arangodb/arangodb:3.10.8 as well. However, we are having the same issue.

from arangodb.

Hello!

I do not think it is related to ArangoDB itself.

An issue like this happens when the ArangoDB Coordinator can't connect to the Agents/DBServers. Often, this issue is caused by DNS setup.

To check the issue - can you share logs from the Operator and Coordinator?

Best Regards,
Adam Janikowski.

from arangodb.

@ajanikow
One of the error was
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/arangodb_operator": stat /usr/bin/arangodb_operator: no such file or directory: unknown

Another error was :
tcp 127.0.0.1:8529: connect: connection refused

from arangodb.

@piyushkumar13 First error is strange, it does not come from crdn pods. You probably have used arangodb image as the image for Operator installation via helm.

Second one is valid error - we just need Operator and CRDN logs to continue (20 last lines)

from arangodb.

The issue is resolved. Seems like it was the access issue at my end. I had limited access on my EKS cluster, which resulted into few of the CRDs/deployments not working properly.

from arangodb.

Great, thanks for letting us know.

from arangodb.