Kimmo Lehto
Kimmo Lehto
Did you try from master branch? (`gem 'k8s-client', github: 'kontena/k8s-client', branch: 'master'` in gemfile) May not make any difference, but maybe it does.
I think it's a good idea as it doesn't make sense to waste efforts in reinventing the wheel and the whole config / initialization interface of k8s-client I think is...
See https://github.com/k8s-ruby/k8s-ruby which is a slightly more active fork of this.
Actually it does not resolve exec command paths the same way: https://github.com/kubernetes/client-go/blob/611184f7c43ae2d520727f01d49620c7ed33412d/tools/clientcmd/loader.go#L579 But the issue is still relevant for the relative certificate paths etc. The load location must be tracked...
Also: Do we actually need the `Dry::Struct` / `Dry::Types` for anything? Couldn't everything just be `K8s::Resource`( which is `< RecursiveOpenStruct`).
Trying to think how it should work. # `K8s::Config` This should actually be something like `K8s::KubeConfig`. It's not a configuration for `K8s::Client`. It's for parsing [kubeconfig files](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) and finding the...
Perhaps the authentication modules should be implemented as some sort of http client library middleware things.
Also, adding to https://github.com/kontena/k8s-client/issues/121#issuecomment-519513084 - There's no sane way to use `Transport.new` that would actually work outside of specs. All of the cert configuration is done in `Transport.config` which builds...