k3s/pkg/server
Brad Davidson dfd0f9d1a6 Correctly report and propagate kubeconfig write failures
As seen in issues such as #15 #155 #518 #570 there are situations where
k3s will fail to write the kubeconfig file, but reports that it wrote it
anyway as the success message is printed unconditionally. Also, secondary
actions like setting file mode and creating a symlink are also attempted
even if the file was not created.

This change skips attempting additional actions, and propagates the
failure back upwards.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
2020-07-24 12:07:32 -07:00
..
auth.go Refactor tokens, bootstrap, and cli args 2019-10-30 19:06:49 -07:00
context.go Update k3s for k8s 1.17.0 2019-12-15 23:28:19 -07:00
router.go Make program name a variable to be changed at compile time 2020-06-06 16:39:41 -07:00
server.go Correctly report and propagate kubeconfig write failures 2020-07-24 12:07:32 -07:00
types.go Add supervisor port 2020-05-05 15:54:51 -07:00