You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And then I have to decide which client instance to use depending on the kind of entity I'm working with. The core client for services, ext client for deployments, batch client for jobs, etc. It'd be nice if this worked like kubectl apply -f some-entity.yml where I could specify the kind and apiVersion fields in my Kubeclient::Resource object and have the client instance figure out which api endpoint to use:
I'm considering writing a wrapper to implement this, but I'd much rather modify kubeclient and contribute those changes upstream instead. Is this something the project would be interested in?
The text was updated successfully, but these errors were encountered:
So I've found myself writing a lot of code like this lately:
And then I have to decide which client instance to use depending on the kind of entity I'm working with. The
core
client for services,ext
client for deployments,batch
client for jobs, etc. It'd be nice if this worked likekubectl apply -f some-entity.yml
where I could specify thekind
andapiVersion
fields in myKubeclient::Resource
object and have the client instance figure out which api endpoint to use:I'm considering writing a wrapper to implement this, but I'd much rather modify kubeclient and contribute those changes upstream instead. Is this something the project would be interested in?
The text was updated successfully, but these errors were encountered: