-
Notifications
You must be signed in to change notification settings - Fork 211
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.
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
docs: show benchmark results for storage capacity tracking #350
docs: show benchmark results for storage capacity tracking #350
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
docs/storage-capacity-tracking.md
Outdated
There were other intermittent problems accessing the apiserver. Tweaking the | ||
way how external-provisioner creates CSIStorageCapacity objects solved this | ||
problem and the same test passed all three times that it was run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What tweaks did you use?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was meant to be a link to kubernetes-csi/external-provisioner#711. I just used the defaults from that updated external-provisioner - text updated.
d6d9639
to
d117785
Compare
/hold Let me add results for 100 nodes with pods that have no volumes... |
This was done in preparation for promoting storage capacity tracking to GA. The csi-driver-hostpath repo seems like a suitable place to hold this text because it showcases how to use the distributed deployment example.
/hold cancel Baseline for 100 nodes was added. The overhead for pods with volumes was actually slightly lower than it was for 10 nodes. |
d117785
to
f053a7b
Compare
/lgtm |
/retest |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This was done in preparation for promoting storage capacity tracking to GA. The
csi-driver-hostpath repo seems like a suitable place to hold this text because
it showcases how to use the distributed deployment example.
Does this PR introduce a user-facing change?: