+++ This bug was initially created as a clone of Bug #1844471 +++ Description of problem: https://github.com/openshift/openshift-apiserver/pull/95 describes a blocker for the 1.19 rebase of openshift-apiserver: upstream k8s.io/apiserver has removed reflection based conversions for performance and correctness reasons (the reflection based conversion was never completely correct). Openshift-apiserver makes use of the old behaviour and we have to fix all API groups. This dependent bug is about the following devex API groups: route.openshift.io
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Stefan, can you clarify what we need to fix? As far as I can tell, none of the errors listed in https://github.com/openshift/openshift-apiserver/pull/95 are related to the route API, and we don't have any conversion functions in https://github.com/openshift/openshift-apiserver/blob/master/pkg/route/apis/route/v1/conversion.go. I tried checking out https://github.com/openshift/openshift-apiserver/pull/95 and running `go test -mod=vendor ./pkg/route/...` and did not get any errors. Can you provide the steps to reproduce the problem that we are expected to fix?
Target reset from 4.6 to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved.
We need this for openshift-apiserver. We cannot move it to 4.7. Increasing priority. This is known since early June.