Add support for relative paths in Kubeconfig

[quite4work]

It is possible to use paths relative to .kube/ in .kube/config, and kubectl also works with relative paths.

Some tools and scripts generate cluster configurations with relative paths by default, which breaks deno-kubernetes_client.

Example config:

# .kube/config
apiVersion: v1
kind: Config
clusters:
- cluster:
    certificate-authority: tls/example/ca.crt
    server: https://192.168.100.101:6443
  name: example
users:
- name: example-admin
  user:
    client-certificate: tls/example/admin.crt
    client-key: tls/example/admin.key

This relates to #9, but I’m not sure if I’ve covered all possible cases.

• Closes Properly handle loading KubeConfig certs/keys #9

[danopia]

Thanks for the contribution. Looks straightforward on first read. I assume the submitted change fixes your usecase successfully?

The wording on #9 was inspired by wanting to keep the RawKubeConfig object as-is, so, storing the recorded path somewhere else instead.. I'd be fine dropping this expectation nowadays.

[danopia]

CI would like you to update deps_jsr.ts as well, since this package is currently published to both registries in parallel.

[quite4work]

Been using this fix since Jun 13, 2023 quite4work@534cd80 (periodically syncing with upstream) - works great.

[danopia]

Tagged as v0.7.4 or https://jsr.io/@cloudydeno/[email protected]