Since I'll need to start a new chain of BZs, I'm re-targeting this at 4.10 and will create appropriate older versions as we roll this change back to 4.6.
*** Bug 2049157 has been marked as a duplicate of this bug. ***
With the current fix, I see the following behavior which I believe is correct but would like confirmation:
# oc api-resources | wc -l
# oc get crd | wc -l
Create 300 custom CRDs and do an oc get on all of them -> no throttling
Create 325 custom CRDs and do an oc get on all of them -> throttled
One thing I see is that as the number of custom CRDs created, the response time for get slows down. In each case below there are no instances returned for oc get <crd>. Average is for 100 oc gets
Custom CRDs created Avg get response
@maszulik Does this look like it is working as you would expect?
(In reply to Mike Fiedler from comment #10)
> @maszulik Does this look like it is working as you would expect?
Yes, the numbers look reasonable. What's important to note is that 4.10+ will also benefit from increased QPS, which unfortunately can't be backported to previous releases.
Marking verified on 4.10 rc2 based on comment 10 and comment 11
Spoke with Poornima Singour on slack, I'm waiting for additional information about their cluster and this particular problem.