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

Allow using Immediate volume binding mode #3525

Open
ctron opened this issue Feb 15, 2024 · 5 comments
Open

Allow using Immediate volume binding mode #3525

ctron opened this issue Feb 15, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@ctron
Copy link

ctron commented Feb 15, 2024

Right now the volume binding mode is hard-coded to WaitForFirstConsumer:

volumeBindingMode: WaitForFirstConsumer

Having that configurable would have provided a workaround for helm/helm#10733

@ctron ctron added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 15, 2024
@BenTheElder
Copy link
Member

You could edit the config of the running deployment, I don't think it makes sense to add another knob here, we should just have a reasonable default.

the default storage driver of clusters is typically not configurable and on the other hand does not have to be used

@BenTheElder
Copy link
Member

The value currently there came from the driver's upstream standard config at the time

@BenTheElder
Copy link
Member

I'm don't think that this toy driver can operate except in this mode, due to the way it "provisions" "volumes".

https://github.com/rancher/local-path-provisioner

@ctron
Copy link
Author

ctron commented Feb 16, 2024

You could edit the config of the running deployment, I don't think it makes sense to add another knob here, we should just have a reasonable default.

Unfortunately that's not possible as the value is considered "immutable".

@BenTheElder
Copy link
Member

It's not possible with an apply but you can get, modify, delete, recreate.

but again, I'm doubtful that this mode even works due to how the PVs are implemented.
It's also not configurable in the upstream chart.

@BenTheElder BenTheElder added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

2 participants