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.

Sign up for GitHub

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

Update config option for openstack block storage #14603

Merged
merged 2 commits into from
May 30, 2019
Merged

Update config option for openstack block storage #14603

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a71937
update config option for openstack block storage
adisky May 29, 2019
a5d3111
Update cloud-providers.md
tengqm May 30, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/en/docs/concepts/cluster-administration/cloud-providers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -294,6 +294,8 @@ and should appear in the `[BlockStorage]` section of the `cloud.conf` file:
there are many Nova availability zones but only one Cinder availability zone.
The default value is `false` to preserve the behavior used in earlier
releases, but may change in the future.
* `node-volume-attach-limit` (Optional): Maximum Number of Volumes that can be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* `node-volume-attach-limit` (Optional): Maximum Number of Volumes that can be
* `node-volume-attach-limit` (Optional): Maximum number of Volumes that can be

(Volume is a Kubernetes resource, number isn't)

attached to the node, default is 256 for cinder.

If deploying Kubernetes versions <= 1.8 on an OpenStack deployment that uses
paths rather than ports to differentiate between endpoints it may be necessary
Expand Down