-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Ephemeral-storage documentation update for plugin requirements #8244
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
Conversation
|
/kind changelog-not-required |
|
please force push and/or reopen pr to trigger changelog check due to issue. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8244 +/- ##
=======================================
Coverage 59.65% 59.65%
=======================================
Files 374 374
Lines 40753 40753
=======================================
Hits 24311 24311
Misses 14960 14960
Partials 1482 1482 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@kaovilai I've corrected the issue. Would appreciate a review or I will just close this in another couple of months. |
|
Will take a look |
|
Closing due to inactivity. |
|
@kaovilai can we get this re-opened? |
Signed-off-by: MICHAEL S FRUCHTMAN <[email protected]>
913e1f6 to
f1e1b7a
Compare
Signed-off-by: MICHAEL S FRUCHTMAN <[email protected]>
Please add a summary of your change
I hit an interesting issue with ephemeral-storage as of late with OCP 4.16.
OCP and similar Kubernetes variations add ephemeral-storage to kubernetes resourceAllocations as options besides CPU and memory. Ignored in most Kubernetes clusters.
Previous versions of OCP did not notice ephemeral-storage usage from plugins as they are finished setting up in the container at startup time. As a result, ephemeral-storage could be set as low as limits of 25Mi or less.
With new installs, ephemeral-storage violations on installation. And eventually tracked down the issue to the /plugins directory.
These estimates are based on current object storage providers. It is entirely possible some plugins will exceed the estimated 100MB per plugin, but this seems to a comfortable estimate at current for some of the more common plugins.
From our own testing of Velero 1.14.1 object storage plugins and a couple of item transformation plugins.
Does your change fix a particular issue?
Documentation for resolving ephemeral-storage plugin requirements seen in OpenShift 4.16 and any other Kubernetes cluster or environment that monitors and restricts ephemeral-storage usage.
Fixes #(issue)
Please indicate you've done the following:
make new-changelog) or comment/kind changelog-not-requiredon this PR.site/content/docs/main./kind changelog-not-required