chore(deps): update dependency container-storage-interface/spec to v1.10.0 #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.3.0
->v1.10.0
Release Notes
container-storage-interface/spec (container-storage-interface/spec)
v1.10.0
Compare Source
What's Changed
Breaking changes/Deprecations
google.golang.org/protobuf
andprotoc-gen-go
libraries were bumped in this release tov1.33.0
(indirectly bumpinggithub.com/golang/protobuf
tov1.5.3
) resulting in breaking changes to generated protobuf go message structures. SPs updating their CSI drivers to this version of the CSI spec must modify their code to handle the changes. See #570.Additions
Clarifications/Corrections/Fixes
Dependencies
New Contributors
Full Changelog: container-storage-interface/spec@v1.9.0...v1.10.0
v1.9.0
Compare Source
Breaking changes/Deprecations:
Additions:
ControllerModifyVolume
RPC and amutable_parameters
field under existingCreateVolumeRequest
RPC to enable modification of volume properties (e.g. IOPS, etc.) after volume creation.Clarifications/Corrections/Fixes:
Dependencies:
genproto
to use the isolated submodule to reduce overall dependency count and avoids future issues with ambiguous imports.Full Changelog: container-storage-interface/spec@v1.8.0...v1.9.0
v1.8.0
Compare Source
Breaking changes/Deprecations:
Additions:
Clarifications/Corrections/Fixes:
Dependencies:
Full Changelog: container-storage-interface/spec@v1.7.0...v1.8.0
v1.7.0
Compare Source
Breaking changes/Deprecations:
Additions:
Clarifications/Corrections/Fixes:
Dependencies:
Full Changelog: container-storage-interface/spec@v1.6.0...v1.7.0
v1.6.0
Compare Source
Breaking changes/Deprecations:
published_node_ids
inGetVolume
by @bswartzAdditions:
maximum_volume_size
field inGetCapacityResponse
from alpha to GA by @pohlyClarifications/Corrections/Fixes:
Dependencies:
New Contributors
Full Changelog: container-storage-interface/spec@v1.5.0...v1.6.0
v1.5.0
Compare Source
Breaking changes/Deprecations:
Additions:
secrets
field toNodeExpandVolumeRequest
.volume_mount_group
field toVolumeCapability
under newVOLUME_MOUNT_GROUP
capability to enable SPs to apply an fsgroup to a volume filesystem duringNodeStageVolume
orNodePublishVolume
operations.SINGLE_NODE_SINGLE_WRITER
andSINGLE_NODE_MULTI_WRITER
, under a newSINGLE_NODE_MULTI_WRITER
capability (intended to replace the existingSINGLE_NODE_WRITER
access mode).Clarifications/Corrections/Fixes:
node_id
fields from 192 to 256.Dependencies:
v1.4.0
Compare Source
Breaking changes/Deprecations:
Additions:
maximum_volume_size
andminimum_volume_size
toGetCapacityResponse
.Clarifications/Corrections/Fixes:
node_id
fields.Dependencies:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.