Upgrade controller-runtime dependency to v0.20.2 to not block downstream module imports

[Jay-Madden]

As controller runtime has deprecated and removed the webhook.Validator interface.

Issue discussing deprecation: kubernetes-sigs/controller-runtime#2596

Deprecation PR: kubernetes-sigs/controller-runtime#2639

Removal PR: kubernetes-sigs/controller-runtime#2877

Keda still uses the webhook.Validator interfaces
https://github.com/search?q=repo%3Akedacore%2Fkeda%20webhook.Validator&type=code

This prevents any downstream codebases attempting to upgrade to v0.20+ from importing the keda apis as the build throws the following error.

/api/v1alpha1/type_webhook.go:40:15: undefined: webhook.Validator

[sivanantha321]

Could this change be considered for the upcoming KEDA v2.17 release? I am happy to contribute and can raise a PR to help with this migration. Let me know if there's a preferred approach or any guidelines I should follow.

[zroubalik]

Thanks for opening this issue

I'd target this to KEDA 2.18. Version 2.17 is gonna be released with k8s v0.31 and If I am not mistaken controller-runtime v0.20 depends on k8s v0.32.

[sivanantha321]

@zroubalik Is there an estimated release timeline for version 2.18?

[sivanantha321]

Keda still uses the webhook.Validator interfaces
https://github.com/search?q=repo%3Akedacore%2Fkeda%20webhook.Validator&type=code
This prevents any downstream codebases attempting to upgrade to v0.20+ from importing the keda apis as the build throws the following error.

@zroubalik Perhaps we could consider migrating the webhook? This would benefit downstream codebases.

[sivanantha321]

/CC @yuzisun

[zroubalik]

Keda still uses the webhook.Validator interfaces
https://github.com/search?q=repo%3Akedacore%2Fkeda%20webhook.Validator&type=code
This prevents any downstream codebases attempting to upgrade to v0.20+ from importing the keda apis as the build throws the following error.

@zroubalik Perhaps we could consider migrating the webhook? This would benefit downstream codebases.

Yeah, this is something we could do.

I'd say the 2.18 will be released in 4 months after 2.17 (we aim to target 3 release per year).

[Jay-Madden]

For what it's worth, because it is generally only the type definition being consumed by downstream codebases, simply migrating the webhook code into the new pattern and merging it would be sufficient as the downstream codebases can simply reference that sha independently of a given release.

[jpfourny]

👁 I'll be watching this closely, since I have a project that requires controller-runtime @ v0.20.x, but it also requires keda. Until the compatibility issue is resolved, I am totally blocked. 🙏

[mycrEEpy]

Until #6700 is merged you could temporary use replace github.com/kedacore/keda/v2 => github.com/mycreepy/keda/v2 v2.0.0-20250410154859-818b39f4fdfe as a workaround to unblock yourself. Works fine in our application.