-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove deprecated autoscaling/v2beta1 HPA objects #865
Conversation
9552647
to
b454f3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -79,12 +68,9 @@ func IsFSGroupChangePolicySupported() bool { | |||
return false | |||
} | |||
|
|||
// NewHPAEmptyObject returns HorizontalPodAutoscaler object for given kubernetes version | |||
// NewHPAEmptyObject returns HorizontalPodAutoscaler object | |||
func NewHPAEmptyObject(opts ...func(obj client.Object)) client.Object { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, we should remove `client.Object from this function and return exact type. It can be done at follow-up commit.
Thanks! |
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 #758 (comment) |
address #864,
since operator supports k8s version from 1.25 now, there is no need to have autoscaling/v2beta1.