Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

capacity: use separate client and lower QPS/Burst settings #711

Merged
merged 1 commit into from
Mar 8, 2022
Merged

capacity: use separate client and lower QPS/Burst settings #711

merged 1 commit into from
Mar 8, 2022

Commits on Mar 7, 2022

  1. capacity: use separate client and lower QPS/Burst settings 

    The rationale behind this change is that it allows external-provisioner to deal
with volumes without being slowed down by the concurrent CSIStorageCapacity
updates. Those updates are less important and the scheduler can deal with
outdated information, so enforcing a lower rate by default is acceptable.

If few changes are needed, updating CSIStorageCapacity keeps up with volume
changes. If many volumes get created or deleted quickly, throttling the
updating is beneficial because multiple changes can be combined into a single
update.

This has helped in practice during a scale test with 100 nodes and 10000
pods+volumes. Without this change, there were intermittent problems with an
unresponsive apiserver. With this change, no such problems occurred.
    @pohly
    pohly committed Mar 7, 2022
    Configuration menu
    Copy the full SHA
    27b6890 View commit details
    Browse the repository at this point in the history