Brad Davidson 3d14092f76 Fix issue with k3s-etcd informers not starting ...

Start shared informer caches when k3s-etcd controller wins leader election. Previously, these were only started when the main k3s apiserver controller won an election. If the leaders ended up going to different nodes, some informers wouldn't be started

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

2024-05-28 15:48:15 -07:00

..

auth

Make /db/info available anonymously from localhost

2024-04-22 19:34:43 -07:00

cert.go

Kubernetes V1.30.0-k3s1 (#10063)

2024-05-06 19:42:27 +03:00

context.go

Kubernetes V1.30.0-k3s1 (#10063)

2024-05-06 19:42:27 +03:00

router.go

Kubernetes V1.30.0-k3s1 (#10063)

2024-05-06 19:42:27 +03:00

secrets-encrypt.go

Kubernetes V1.30.0-k3s1 (#10063)

2024-05-06 19:42:27 +03:00

server.go

Fix issue with k3s-etcd informers not starting

2024-05-28 15:48:15 -07:00

token.go

Move etcd snapshot management CLI to request/response

2024-04-09 15:21:26 -07:00

types.go

Move DisableServiceLB/Rootless/ServiceLBNamespace into config.Control

2022-09-30 08:17:20 -07:00