Closed tusharvaswani714 closed 3 weeks ago
I can confirm that I am getting some variants of the same error
{"level":"ERROR","time":"2024-08-29T05:01:14.280Z","logger":"webhook","message":"http: TLS handshake error from 192.168.132.135:48102: read tcp 192.168.137.84:8443->192.168.132.135:48102: read: connection reset by peer\n","commit":"62a726c"}
{"level":"ERROR","time":"2024-08-29T05:07:16.974Z","logger":"webhook","message":"http: TLS handshake error from 192.168.132.135:46286: EOF\n","commit":"62a726c"}
Karpenter 1.0.1 EKS 1.29
I get similar error:
{"level":"ERROR","time":"2024-09-10T00:53:17.289Z","logger":"webhook","message":"http: TLS handshake error from 10.129.177.41:39324: EOF\n","commit":"6e9d95f"} │
Karpenter 0.37.2 EKS 1.29
Also with this update we start switching from AL2 to Bottlerocket, thou disruption budget blocks the actual switch for now.
This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity.
Hey everyone, I am trying to setup karpenter 1.0.1 on my cluster. I tried to deploy a microservice. It did launch ec2 instances so that setup part was atleast working good. But it didn't place the pod on that instance and nodeclaim status was unknown and after some time it terminated instance and relaunched new one. These are the logs from karpenter:
I am mainly suspicious because of this error log: