Open frank-bee opened 11 months ago
@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 . Better do not skip these annotations, because if they are there, probably they are not "optionally" (like in our case). I think we will try to reduce the characters in these 2 substrings (service , release):
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