mirror of
https://github.com/gravitational/teleport
synced 2024-10-21 17:53:28 +00:00
1d37ede936
Teleport will fail to start when when a k8s cluster is unavailable when using the kubeconfig in a `kubernetes_service` configuration. This means that a single missing cluster can disrupt _all_ of the configured clusters, even if the others are online. This change makes failing the cluster credential enumeration a per-k8s-cluster warning, rather than a stop-the-world error. It also expands the testing shims inside the k8s proxy to allow more sophisticated mocked scenarios, in order to test the above. See-Also: #7215 |
||
|---|---|---|
| .. | ||
| acme.go | ||
| cfg.go | ||
| cfg_test.go | ||
| connect.go | ||
| db.go | ||
| info.go | ||
| kubernetes.go | ||
| listeners.go | ||
| service.go | ||
| service_test.go | ||
| signals.go | ||
| state.go | ||
| state_test.go | ||
| supervisor.go | ||