You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: I'm not sure where this issue belongs. So there is a duplicate on the primary crossplane repo just in case: crossplane/crossplane#3224
What happened?
Kubernetes object names (.metadata.name) supports a maximum length of 253 characters.
Kubernetes Label values (.metadata.labels[]) are limited to 63 characters in length.
Therefore if your ProviderConfig has a name that is > 63 charcters when you attempt to use it crossplane will block you with errors such as:
'connect failed: cannot track provider config usage: cannot apply ProviderConfigUsage:
cannot create object: ProviderConfigUsage.helm.crossplane.io "5156973e-c7fc-4b6f-9697-8f0aea08d75f"
is invalid: metadata.labels: Invalid value: "xx-xxxxxxxxxxxxxxxxxx-xxxxx-xxxxx-xxxxxx-xxxxxxxx-xx-xxxx-x-xxx-xx":
must be no more than 63 characters'
How can we reproduce it?
Create a providerconfig with a name longer than 63 characters and then try and use it.
What environment did it happen in?
Crossplane version:
v1.6.3
The text was updated successfully, but these errors were encountered:
NOTE: I'm not sure where this issue belongs. So there is a duplicate on the primary crossplane repo just in case: crossplane/crossplane#3224
What happened?
Kubernetes object names (.metadata.name) supports a maximum length of 253 characters.
Kubernetes Label values (.metadata.labels[]) are limited to 63 characters in length.
Therefore if your ProviderConfig has a name that is > 63 charcters when you attempt to use it crossplane will block you with errors such as:
How can we reproduce it?
Create a providerconfig with a name longer than 63 characters and then try and use it.
What environment did it happen in?
Crossplane version:
v1.6.3
The text was updated successfully, but these errors were encountered: