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

Add support for volumeAttributesClassName in storage configuration #10462

Open
scholzj opened this issue Aug 16, 2024 · 3 comments
Open

Add support for volumeAttributesClassName in storage configuration #10462

scholzj opened this issue Aug 16, 2024 · 3 comments

Comments

@scholzj
Copy link
Member

scholzj commented Aug 16, 2024

VolumeAttributesClass introduces to Kubernetes new way how to manage the performance class of the PVCs. Unlike a Storage Class that is immutable, the Volume Attributes Class allows users more flexibility when configuring parameters of the storage such as IOPS, throughput etc. This is something what comes up from time to time from a Strimzi users in our forum. Currently, it is often managed through various annotations. It would be nice to support the configuration of the VolumeAttributesClass / volumeAttributesClassName in PVCs and in out storage configuration.

@scholzj
Copy link
Member Author

scholzj commented Aug 22, 2024

Discussed on a community call on 22.8.2024:This would be a useful feature. A proposal should be written to clarify the API changes, storage diffing changes etc.

@venkatesh2090
Copy link
Contributor

Hi, I would like to have a go at this.

Do you reckon this is easy enough for someone new to the code base. I have been able to provision clusters with this feature enabled on AWS, so I am fine with testing this. Couldn't figure it out locally though since the CSI driver for kind doesn't seem to respect this API.

@scholzj
Copy link
Member Author

scholzj commented Jan 9, 2025

I do not think this would be too complicated. But as it would include some changes to the API, this needs to have a proposal first. So you would need to start with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants