Hi @AG_AOSM - welcome to Speckle’s community. If you haven’t already, feel free to introduce yourself to the community. We’d love to know more about what you are using Speckle for and where you are using it - it really helps us understand how we can guide Speckle’s future to better help the community. Hopefully we can debug your issues and get you going.
From the logs you posted, the speckle-server Pod has successfully connected to Postgres and Redis. I believe we can ignore those.
The 503 (Service Unavailable) message you seen in the frontend is often returned by a load balancer when it is unable to connect to the server pods. This may be because they are reporting unready and so the load balancer has no ready pods to connect to. It seems as if the problem is with ingress to speckle-server.
To begin with, I would suggest disabling all network policy rules. This should help eliminate that as the source of your issues.
Are there errors being shown when you kubectl describe the speckle-server pods? Kubernetes should be logging the errors with the liveness & readiness probes.
Have you enabled the Helm test, and what are the logs that it shows?
It’s been a few years since I deployed to EKS, but hopefully there are others in the community that are more familiar and can help out with those specifics.
Iain