There is now a community fork of the kontena/k8s-client under a community organization k8s-ruby.
The k8s-ruby library is a community effort to keep k8s-client maintained without any dependencies to the former Kontena.io organization which said farewell at the end of 2019. The library was renamed in order to publish it to Rubygems without conflicting with k8s-client.
It would be wonderful to combine the maintainership for Kubernetes' Ruby projects under a common organization, be it k8s-ruby or something else.
It would make sense to extract eg. the authentication logic and other common parts under a Gem of its own. Ultimately it would be great to kill the k8s-ruby gem and replace it with k8s-auth, k8s-api-client, k8s-resource and such smaller building blocks.
There is now a community fork of the kontena/k8s-client under a community organization k8s-ruby.
The k8s-ruby library is a community effort to keep k8s-client maintained without any dependencies to the former Kontena.io organization which said farewell at the end of 2019. The library was renamed in order to publish it to Rubygems without conflicting with k8s-client.
It would be wonderful to combine the maintainership for Kubernetes' Ruby projects under a common organization, be it k8s-ruby or something else.
It would make sense to extract eg. the authentication logic and other common parts under a Gem of its own. Ultimately it would be great to kill the k8s-ruby gem and replace it with k8s-auth, k8s-api-client, k8s-resource and such smaller building blocks.