k3s/pkg/cluster
Brad Davidson 8ad7d141e8 Close etcd clients to avoid leaking GRPC connections
If you don't explicitly close the etcd client when you're done with it,
the GRPC connection hangs around in the background. Normally this is
harmelss, but in the case of the temporary etcd we start up on 2399 to
reconcile bootstrap data, the client will start logging errors
afterwards when the server goes away.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
2021-12-17 23:55:17 -08:00
..
managed etcd snapshot functionality enhancements (#4453) 2021-11-29 10:30:04 -08:00
bootstrap_test.go Secrets-encryption rotation (#4372) 2021-12-07 14:31:32 -08:00
bootstrap.go Close etcd clients to avoid leaking GRPC connections 2021-12-17 23:55:17 -08:00
cluster.go Secrets-encryption rotation (#4372) 2021-12-07 14:31:32 -08:00
encrypt.go Fix spelling to satisfy codespell check 2021-07-01 13:29:03 -07:00
etcd.go delete nocluster file and remove build tag 2021-04-07 12:16:28 -07:00
https.go Add cert rotation command (#4495) 2021-12-02 23:19:16 +02:00
managed.go fix a runtime core panic (#3627) 2021-07-13 23:33:07 +02:00
router.go Add a bunch of doc comments 2020-09-27 03:10:00 -07:00
storage.go Close etcd clients to avoid leaking GRPC connections 2021-12-17 23:55:17 -08:00