boz/kail

Adapt deployment selector to k8s v1.16

timebertt opened this issue · 4 comments

timebertt commented

The kail deployment selector does not work for Kubernetes v1.16.

For example:
I have some running deployments (all healthy) in the current namespace:

$ k get deploy
NAME                         READY   UP-TO-DATE   AVAILABLE   AGE
[...]
grafana-operators            1/1     1            1           39m
grafana-users                1/1     1            1           39m
kibana-logging               1/1     1            1           40m
kube-apiserver               1/1     1            1           44m
kube-controller-manager      1/1     1            1           44m
[...]

When I now try to use kail for the kube-apiserver deployment it does not work:

$ kail --current-ns -d kube-apiserver -c kube-apiserver
ERRO[0000] client list: the server could not find the requested resource  cmp=lister
ERRO[0000] lister error: client list: the server could not find the requested resource  cmp=controller
^Ckail: error: Unable to initialize data source

I guess, this is related to the recent changes in k8s v1.16, as the extensions/v1beta1.Deployment resource is now completely removed (see https://kubernetes.io/blog/2019/09/18/kubernetes-1-16-release-announcement/)

$ k version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T23:42:50Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
$ kail version
0.12.0 (0d6900b110161d93625ba4fc6ac8fe7f0e8fe781)
boz commented

Thanks @tim-ebert for the detailed report.

I've just started to notice this myself :-/ I'll try to get to it ASAP.

  • 👍1
timebertt commented

@boz Nice, thank you very much :)

florianrusch commented

Same problem with replica-sets --rs

carlossg commented

This is fixed with boz/kcache#3

  • 👍1