-
Notifications
You must be signed in to change notification settings - Fork 672
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] Add information about behaviors of resource defaults and limits #2513
Comments
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏 |
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏 |
the entire config system is getting overhauled. cc @katrogan ? |
only a proposal for now https://github.com/flyteorg/flyte/blob/master/rfc/system/3749-sane-overridable-defaults.md but this issue is specifically for explaining what the config options mean (there is confusion between requests and defaults) |
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. |
Commenting to keep it open as this is still unresolved |
Description
We need clearer documentation about how Flyte sets resource defaults and limits.
From @katrogan :
For full details, see the Slack thread below.
References:
https://flyte-org.slack.com/archives/C03CY9S9MFE/p1652970945750369
https://docs.flyte.org/en/latest/concepts/admin.html#task-resource-defaults
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: