Skip to content
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

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

Haleygo
Copy link
Contributor

@Haleygo Haleygo commented Feb 7, 2024

address #864,
since operator supports k8s version from 1.25 now, there is no need to have autoscaling/v2beta1.

@Haleygo Haleygo requested a review from f41gh7 February 7, 2024 04:57
@Haleygo Haleygo requested a review from Amper as a code owner February 7, 2024 04:57
Copy link
Collaborator

@f41gh7 f41gh7 left a 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 {
Copy link
Collaborator

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.

@f41gh7 f41gh7 merged commit 38dfad5 into master Feb 7, 2024
2 checks passed
@f41gh7 f41gh7 deleted the remove-deprecated-beta-hpa branch February 7, 2024 07:42
@f41gh7
Copy link
Collaborator

f41gh7 commented Feb 7, 2024

Thanks!

@jicki
Copy link

jicki commented Feb 22, 2024

@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
Copy link
Collaborator

f41gh7 commented Feb 23, 2024

@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 #758 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants