panic: rpc error: code = Unavailable desc = error reading from server

[grosser]

Description

Observed Behavior:

{"message":"panic: rpc error: code = Unavailable desc = error reading from server: read tcp 10.222.118.58:43588-\u003e10.222.118.25:2379: read: connection timed out"}
{"message":""}
{"message":"goroutine 1 [running]:"}
{"message":"github.com/samber/lo.must({0x31f1ba0, 0x4000c82780}, {0x0, 0x0, 0x0})"}
{"message":"\tgithub.com/samber/lo@v1.50.0/errors.go:53 +0x1c8"}
{"message":"github.com/samber/lo.Must0(...)"}
{"message":"\tgithub.com/samber/lo@v1.50.0/errors.go:72"}
{"message":"github.com/aws/karpenter-provider-aws/pkg/operator.NewOperator({0x3bf3790, 0x40004c2bd0}, 0x400069bb40)"}
{"message":"\tgithub.com/aws/karpenter-provider-aws/pkg/operator/operator.go:108 +0x11c"}
{"message":"main.main()"}
{"message":"\tgithub.com/aws/karpenter-provider-aws/cmd/controller/main.go:31 +0x28"}.

Expected Behavior:
regular error

Reproduction Steps (Please include YAML):
don't know how it got triggered

Versions:

• Chart Version: 1.5.0
• Kubernetes Version (kubectl version): v1.31.10

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment