[go: nahoru, domu]

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

ProviderConfigUsage creation blocked because providerconfig name > 63 characters #345

Open
SleepyBrett opened this issue Aug 5, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@SleepyBrett
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant