I don't see any '4.9' yet, so using '4.8' for now for target release.
> I don't see any '4.9' yet, so using '4.8' for now for target release. 4.8 is in feature freeze, but release-4.8 branches are still being fast-forwarded to track main/master until closer to code freeze. So everything that is landing now is still going out with 4.8 when it GAs, and 4.8.0 as a target release is appropriate.
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-04-15-202330 True False 118m Cluster version is 4.8.0-0.nightly-2021-04-15-202330 $ oc get flowschema | grep probe probes exempt 2 <none> 142m False $ oc edit kubeapiserver/cluster # change the loglevel to TraceAll kubeapiserver.operator.openshift.io/cluster edited After the kube-apiservers fnished the restarting, make some readyz requests to the apiserver, $ for i in {1..30}; do curl -k https://api.kewang-man1681.qe.gcp.devcluster.openshift.com:6443/readyz;done $ kas_pods=$(oc get pods -n openshift-kube-apiserver | grep 'kube-apiserver' | awk '{print $1}'); for pod in $kas_pods; do oc -n openshift-kube-apiserver logs $pod -c kube-apiserver | grep 'exempt' | grep 'readyz' | head -1;done I0416 06:05:33.220514 20 apf_controller.go:792] startRequest(RequestDigest{RequestInfo: &request.RequestInfo{IsResourceRequest:false, Path:"/readyz", Verb:"get", APIPrefix:"", APIGroup:"", APIVersion:"", Namespace:"", Resource:"", Subresource:"", Name:"", Parts:[]string(nil)}, User: &user.DefaultInfo{Name:"system:anonymous", UID:"", Groups:[]string{"system:unauthenticated"}, Extra:map[string][]string(nil)}}) => fsName="probes", distMethod=(*v1beta1.FlowDistinguisherMethod)(nil), plName="exempt", immediate The new flowschema probes works as expected, so move the bug VERIFIED.
https://github.com/openshift/cluster-kube-apiserver-operator/pull/1099 must get in first, we need to revert the flow schema from the 'Manifests' folder first, otherwise we don't know who is creating the flow schema object, is it cvo or kube-apiserer? (This is due to the fact that we did not wait for the upstream PR to merge, we went ahead and added a similar flowschema in manifests folder)
> ... we need to revert the flow schema from the 'Manifests' folder first, otherwise we don't know who is creating the flow schema... No need to block on 1099, because, as bug 1956606 points out, the manifest is being ignored by the CVO and has been since it landed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438