-
Notifications
You must be signed in to change notification settings - Fork 19
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
resource volume - objectionable restriction on parameter labels #646
Comments
Thanks for the report, we're taking a look at this. |
Checked back with the responsible team: The label values are restricted by definition as follows:
These are same restrictions as for kubernetes label values This is however missing from the API, CLI and the terraform documentation |
Besides the fact that kubernetes allows dots in labels Valid label value: this is not part of the kubernetes description: All characters must use UTF-8 encoding, and international characters are allowed. How is the encoding of international characters to pass the regex filter ^(-|_|[a-z0-9]){0,63}$ ? If I use UTF-8 code units, labels are restricted to 32 characters only. (example: /opt/mstr -> 2F 6F 70 74 2F 6D 73 74 72 C3 B6). Other encodings are not possible. Is there a reason to restrict resources, which are independent of kubernetes usage, to kubernetes specifics? |
You can ignore my last question. I just discovered, that the resource server has the same restriction with labels. That is the next bigger problem for us. We use labels for example in server maintenance and monitoring. So at least 4-5 labels, which we use at the moment with VMs based on the openstack provider, will be not be usable any longer. |
Creating a volume with a label as described below
leads to this error:
After changing /opt/mstr to _opt_mstr the deployment succeeds, but is not useful anymore.
The IaaS-API (https://docs.api.stackit.cloud/documentation/iaas/version/v1#tag/Volumes/operation/v1CreateVolume) has no restrictions on parameter labels.
BTW even the example response with label "foo" = "Foo Value", shown in the API-doc, would not be possible with the restriction shown in the error message 😀
The text was updated successfully, but these errors were encountered: