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
..
aws_metadata_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
aws_metadata.go	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
kms_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
kms.go	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
secretskms_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
secretskms.go	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
vault_sa_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
vault_sa.go	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
vault_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
vault_tokens_test.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00
vault_tokens.go	util: NewK8sClient() should not panic on non-Kubernetes clusters	2021-09-02 11:22:14 +00:00
vault.go	cleanup: move KMS functionality into its own package	2021-08-30 16:31:40 +00:00