Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Incompatibility between kubectl and Kubernetes cluster version results in misleading error #426
I recently (mostly accidentally) tried using kubectl 1.9.x against a 1.6.x cluster. Kubernetes doesn't seem to promise anything about what will happen in this situation (but I haven't found great compatibility guidelines). What did happen is that
This made it look like there was some application logic error in telepresence, where it attempted to operate on a non-existent resource. I couldn't figure out how this could happen. Eventually, I added
This makes it clear that the resource has nothing to do with telepresence logic and is all about basic communication between kubectl and the cluster.
Ideally, I would like to see telepresence tell me that my kubectl is incapable of talking to my kubernetes cluster. I'm not exactly sure how this situation can be reliably detected (considering an incompatibility can presumably take any form and therefore manifest any kind of failure). Perhaps reporting more information in the telepresence log is the best we could actually do.
This was encountered in the course of development of #418 (wherein I blindly set up CI with the latest kubectl without consideration of with which server version the tests would interact). The misconfiguration was then exacerbated by the fact by default I had no interactive access to the environment and was making no other use of
We can warn if we see widely divergent version numbers when we run
If we fire off a bunch of