Open kke opened 4 years ago
Actually it does not resolve exec command paths the same way:
But the issue is still relevant for the relative certificate paths etc. The load location must be tracked and in case the command has path separators, and is not absolute?
, the load origin must be known.
Any relative file references are supposed to be searched for under the directory of the kubeconfig file that defined the reference.
client-go
usesfilepath.isAbs()
, the javascript lib usespath.isAbsolute()
.k8s-client
should probably use thePathname#absolute?
to build the final path.For example when merging kubeconfigs, the origin of each entry must be tracked so the reference can be resolved later.