The Problem:
The Env0 agent is currently on version 1.23. K8s version 1.24 is scheduled for end of life in July of 2023. According to Env0's own documentation
Supported versions
The kubectl version is 1.23, and the kustomize version is 4.5.4.
It is recommended for the remote cluster not to be more than 1 minor version ahead or behind the client's.
This means that anyone using Azure will be outside the recommended compatibility range of the Env0 Kubectl client. Furthermore, it limits any customer upgrades to 1.25 because of the api changes with HPAs in version 1.26.
The Solution
IMO, it's unrealistic to imagine that you can satisfy the whims of every one of your clients with a single pre-installed Kubectl version. We run into the same problem with Terraform, but instead of installing any particular version of Terraform, you use tfenv to manage the Terraform binaries. There's a similar project for kubectl called kbenv that employs the same usage pattern.
I would really like to see the ability to run whatever kubectl version I need, just like I can do with Terraform.
The Problem:
The Env0 agent is currently on version 1.23. K8s version 1.24 is scheduled for end of life in July of 2023. According to Env0's own documentation
This means that anyone using Azure will be outside the recommended compatibility range of the Env0 Kubectl client. Furthermore, it limits any customer upgrades to 1.25 because of the api changes with HPAs in version 1.26.
The Solution
IMO, it's unrealistic to imagine that you can satisfy the whims of every one of your clients with a single pre-installed Kubectl version. We run into the same problem with Terraform, but instead of installing any particular version of Terraform, you use tfenv to manage the Terraform binaries. There's a similar project for kubectl called kbenv that employs the same usage pattern.
I would really like to see the ability to run whatever kubectl version I need, just like I can do with Terraform.