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

Backport of docs: clarify capacity_min/max for volumes into release/1.2.x #12827

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #12825 to be assessed for backporting due to the inclusion of the label backport/1.2.x.

The below text is copied from the body of the original PR.


Fixes #12821

The capacity fields for create volume set bounds on the resulting
size of the volume, but the ultimate size of the volume will be
determined by the storage provider (between the min and max). Clarify
this in the documentation and provide a suggestion for how to set a
exact size.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/docs-csi-volume-capacity/positively-concise-goblin branch from 520c046 to f0fa6c2 Compare April 29, 2022 17:38
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 28ebd2d into release/1.2.x Apr 29, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/docs-csi-volume-capacity/positively-concise-goblin branch April 29, 2022 17:38
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants