Closed Haleygo closed 7 months ago
Thanks!
@f41gh7 @Haleygo Deleting the old autoscaling/v2beta1 will affect subsequent version upgrades for k8s clusters that cannot be upgraded. Is it more appropriate to use compatible adaptation to solve this problem?
@f41gh7 @Haleygo Deleting the old autoscaling/v2beta1 will affect subsequent version upgrades for k8s clusters that cannot be upgraded. Is it more appropriate to use compatible adaptation to solve this problem?
Unfortunately, it's not possible to support EoL versions of kubernetes properly.
I think, soon we're going to redesign resource reconciliation a bit. It must fix possible errors with incompatible resources.
If resource don't use deprecated API directly, it shouldn't trigger any errors by calling deprecated kubernetes APIs.
Related issue https://github.com/VictoriaMetrics/operator/issues/758#issuecomment-1729257683
address https://github.com/VictoriaMetrics/operator/issues/864, since operator supports k8s version from 1.25 now, there is no need to have autoscaling/v2beta1.