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

Character set for labels (key/value pairs) #581

Open
1 task done
yoichih52 opened this issue Mar 3, 2025 · 2 comments
Open
1 task done

Character set for labels (key/value pairs) #581

yoichih52 opened this issue Mar 3, 2025 · 2 comments
Assignees

Comments

@yoichih52
Copy link

Page URL

https://docs.netapp.com/us-en/trident/trident-concepts/virtual-storage-pool.html

Page title

Virtual pools

Summary

・This page contains information about the labels (key/value pairs) that are specified when using Trident's storage pool function.

・To make it easier for users to understand, please provide information about the character set that can be specified for labels (key/value pairs) when using Trident's storage pool function.

・I believe the character set that can be specified for labels (key/value pairs) when using Trident's storage pool function is as follows.

Available characters : "0-9, A-Z, a-z, _, -"

Example)
Correct : selector: "backend=test-012"
Incorrect : selector: "backend=test.012"

Public issues must not contain sensitive information

  • This issue contains no sensitive information.
@yasuoo-netapp
Copy link

I believe that using characters other than the ones mentioned above as a Label will not cause an error,
but I think the Operators will not be able to handle it correctly based on the following code.

https://github.com/NetApp/trident/blob/master/storage_attribute/label.go#L14-L19

I would also appreciate it if the permissible characters could be explicitly stated.

Thanks.

@netapp-aruldeepa netapp-aruldeepa self-assigned this Mar 3, 2025
@netapp-aruldeepa
Copy link
Contributor

Hi @yasuoo-netapp,

Thanks for sharing the information.
We will work with our team and update the documentation as required.

Regards,
Deepa

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

No branches or pull requests

3 participants