Kubeflow on OpenShift 4.12(and higher?) compatibility

[Feelas]

Hello Team,
are there any plans to re-validate Kubeflow on versions newer than 4.9, maybe even up to 4.12 and beyond?

When we tried deploying on OpenShift 4.11 (based of K8s 1.25) we are not facing many issues.
Since OpenShift 4.12+ is based on K8s 1.25+, there are some issues during the installation:

Warning: autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler
[...]
resource mapping not found for name: "istio-ingressgateway" namespace: "istio-system" from "STDIN": no matches for kind "PodDisruptionBudget" in version "po
licy/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "istiod" namespace: "istio-system" from "STDIN": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "eventing-webhook" namespace: "knative-eventing" from "STDIN": no matches for kind "PodDisruptionBudget" in version "po
licy/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "tekton-pipelines-webhook" namespace: "kubeflow" from "STDIN": no matches for kind "HorizontalPodAutoscaler" in version
 "autoscaling/v2beta1"

These messages look like they are connected to the dropped PodDistruptionBudget v1beta1 being discontinued on 1.25 (kubernetes-sigs/metrics-server#1104). same for the HorizontalPodAutoscaler, which on 1.26+ will be unavailable even as v2beta2 API (as noticed) and here it is still v2beta1 version.
These issues are bordering on critical (most likely it would be better for HPA & PDB to be used) but don't seem to block the KF installation fully.

Thanks for any possible clarification on whether you're planning to support newer versions or not :)