Skip to content

Add GRPC ControllerModifyVolumeTopology for KEP-5381 #593

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

iltyty
Copy link

@iltyty iltyty commented Jun 25, 2025

What type of PR is this?
Feature

What this PR does / why we need it:
This PR adds a new GRPC ControllerModifyVolumeTopology to support KEP #5381.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
This is an alternative for PR #592.

Does this PR introduce an API-breaking change?:

none

@iltyty iltyty changed the title Allow modifying volume topology Add GRPC ControllerModifyVolumeTopology for KEP-5381 Jun 25, 2025
@xing-yang
Copy link
Contributor

It will be great if you can also update the KEP and describe how this new PRC will be used in Kubernetes.

// parameters it intends to modify. SPs MUST NOT modify volumes based
// on the absence of keys, only keys that are specified should result
// in modifications to the volume.
map<string, string> mutable_parameters = 3;
Copy link
Contributor

Choose a reason for hiding this comment

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

If we are modifying topology, why will the request not contain newer accessibility_requirements ?

Copy link
Author

@iltyty iltyty Jul 1, 2025

Choose a reason for hiding this comment

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

We wanted SPs to determine the volume topologies according to the volume type and/or other information. Also, adding this field will result in several issues. E.g., we need to decide the priority between this field and the one in CreateVolume.

@iltyty
Copy link
Author

iltyty commented Jul 1, 2025

It will be great if you can also update the KEP and describe how this new PRC will be used in Kubernetes.

ok, will update

@iltyty iltyty force-pushed the kep-5381-new-grpc branch from 6bc8ad2 to cf0b28d Compare July 1, 2025 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants