Pick UPSTREAM PR 102171 - Implement support for watch initialization in P&F
> I0617 14:44:09.547150 24817 round_trippers.go:463] X-Kubernetes-Pf-Flowschema-Uid: 8be0f28c-e930-4351-87e0-677920e0fb00
> I0617 14:44:09.547174 24817 round_trippers.go:463] X-Kubernetes-Pf-Prioritylevel-Uid: 6404918d-67a9-4b25-b5ed-276ef5966840
Yes, this proves that p&f is taking into account WATCH request as well.
another verification step you can do is make sure other long running requests (excluding WATCH) are not included, for example if you do pods/log.
Talked to email@example.com in Slack, he will discuss with PerfScale Engineering team in meeting about the performance and long running tests. Based on Comments #3 and #4, the PR fix works fine, so move the bug VERIFIED.
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.