-
Notifications
You must be signed in to change notification settings - Fork 357
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
Generated Ingress annotation too long #1385
Comments
@frank-bee thanks a lot for creating this issue! I guess what we can do is to add logic to skip annotations that would exceed the limit so that the ingress is able to sync, but the problem that the condition doesn't apply to the service would remain, so I'm unsure how we would fix this as there seems to be a general Kubernetes limitation on this / bad design by AWS ingress-controller that has problems with long service names |
Fully agree to what you say, @FabianKramm . alb.ingress.kubernetes.io/conditions.service-name-x-istio-system-x-vcluster-release-name |
@frank-bee yeah that sounds like a short term workaround at least until we find an actual solution |
What happened?
This error is thrown when creating an Ingress annotation.
The annotation is as follows
What did you expect to happen?
The Ingress should be created in the host cluster incl. this annotation
How can we reproduce it (as minimally and precisely as possible)?
Create an ingress with an annotation key longer than allowed
Anything else we need to know?
See also https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/#syntax-and-character-set
Host cluster Kubernetes version
Host cluster Kubernetes distribution
vlcuster version
Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)
default
OS and Arch
locally I work with a MAc
The text was updated successfully, but these errors were encountered: