[Improvement] Operator should support K8S 1.24
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Search before asking
- [X] I have searched in the issues and found no similar issues.
What would you like to be improved?
In K8S operator, we use autoscaling/v2beta2, in K8S 1.24, they remove autoscaling/v2beta2, they have autoscaling/v2.
How should we improve?
We should adapt to 1.24. I don't know whether we can adapt to the old versions.
Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
@advancedxy @wangao1236 Could you give me some input?
I have a solution. https://github.com/VictoriaMetrics/operator/blob/master/controllers/factory/k8stools/version.go
1.24 is already end of life^1. I think the master code should target the latest K8S version instead.
However there might be some pretty old k8s clusters runnings in the prod. @wangao1236 do you have any idea about the backward compatibility of K8S versions? Is it safe for operator to depends on a newer version of k8s and deploys to an old one with limited usage of new APIs.
@zhengchenyu @qijiale76 Could you have any ideas?