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.

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

Should volume formatting be included in pod startup time? #706

Open
wojtek-t opened this issue Jul 30, 2019 · 2 comments
Open

Should volume formatting be included in pod startup time? #706

wojtek-t opened this issue Jul 30, 2019 · 2 comments
Labels
area/clusterloader area/slo lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@wojtek-t
Copy link
Member

Forked from: #657

from @msau42

This discussion also brought up an interesting point. We are not measuring provisioning time because we said that is bootstrapping behavior that only happens the first time.

We also format the filesystem the first time we mount the volume on any node and that is something this test will currently measure during pod startup. Is it something we want to include? If not, then we would need to bring up pods twice and only measure the second time

/area slo
/are clusterloader

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2019
@wojtek-t
Copy link
Member Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterloader area/slo lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants