Cluster information:
Kubernetes version: v1.19.4
Cloud being used: bare-metal
Host OS: centos7.6
Scenes:
I hope to differentiate isolation protection according to users or namespaces, different users or namespaces will use different PL policies, but according to the current situation, every time a PL is added, modified or deleted, the ConcurrencyLimit of other PLs at the same level will change. , cannot be isolated from each other. (Note: The total number is fixed, and the number of users or namespaces that can be supported will be constrained in advance)
so:
I hope that in the case of a fixed total number, I can adjust the queue length according to a fixed value, and can see the number of waiting, execution, and remaining available in the queue
We are now working on changes in this area, but not sure if such changes are reasonable