Coder.com•3y ago

Kubernetes Pod recreation causing issue.

We are 100% on spot instances for our EKS cluster and I'm trying to manage kubernetes pod with Kuberentes deployment to make sure Pod get self heal whenever it's get re-created. Looks like it's causing issue because of Pod name changes every time it gets recreated and Coder throws error

"error": update replica:  github.com/coder/coder/enterprise/replicasync.(*Manager).syncReplicas /home/runner/work/coder/coder/enterprise/replicasync/replicasync.go:292         - sql: no rows in result set

"error": update replica:  github.com/coder/coder/enterprise/replicasync.(*Manager).syncReplicas /home/runner/work/coder/coder/enterprise/replicasync/replicasync.go:292         - sql: no rows in result set

2 Replies

jbot_26OP•3y ago

If I stop and re-start workspace it works fine after that. 🤔 May be I need to make sure I have correct resource ID?

jbot_26OP•3y ago

I just confirmed I have same as in this example https://coder.com/docs/coder-oss/latest/templates/resource-metadata#example

Resource Metadata - Coder OSS main docs

Learn how to expose resource data to users

Gaming

Programming

Kubernetes Pod recreation causing issue.

Did you find this page helpful?