Niels de Vos 60c2afbcca util: NewK8sClient() should not panic on non-Kubernetes clusters ... When NewK8sClient() detects and error, it used to call FatalLogMsg() which causes a panic. There are additional features that can be used on Kubernetes clusters, but these are not a requirement for most functionalities of the driver. Instead of causing a panic, returning an error should suffice. This allows using the driver on non-Kubernetes clusters again. Fixes: #2452 Signed-off-by: Niels de Vos <ndevos@redhat.com>		2021-09-02 11:22:14 +00:00
..
cephfs	cephfs: remove explicit size setting of cloned volume	2021-09-01 09:32:29 +00:00
controller	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
csi-common	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
journal	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
kms	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
liveness	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
rbd	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
util	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00