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

"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

Kubernetes Pod recreation causing issue.

Similar Threads

Similar Threads

Similar Threads