From a6db141216d6e64c1ab2f846492c57656ef7db8d Mon Sep 17 00:00:00 2001 From: deads2k Date: Fri, 29 Jan 2016 07:50:54 -0500 Subject: [PATCH] explain kubeconfig path loading rules --- docs/user-guide/kubeconfig-file.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/user-guide/kubeconfig-file.md b/docs/user-guide/kubeconfig-file.md index cf0db4f6158..9110c40148e 100644 --- a/docs/user-guide/kubeconfig-file.md +++ b/docs/user-guide/kubeconfig-file.md @@ -247,6 +247,11 @@ The rules for loading and merging the kubeconfig files are straightforward, but 1. The command line flags are: `client-certificate`, `client-key`, `username`, `password`, and `token`. 1. If there are two conflicting techniques, fail. 1. For any information still missing, use default values and potentially prompt for authentication information + 1. All file references inside of a kubeconfig file are resolved relative to the location of the kubeconfig file itself. When file references are presented on the command line + they are resolved relative to the current working directory. When paths are saved in the ~/.kube/config, relative paths are stored relatively while absolute paths are stored absolutely. + +Any path in a kubeconfig file is resolved relative to the location of the kubeconfig file itself. + ## Manipulation of kubeconfig via `kubectl config `