Open jeraldsm opened 2 years ago
Hi, This is currently due to a limitation of EKS. Since these configuration settings are merged into a single fluent bit configuration file and there is some template logic that currently has a line restriction. Our team doesn't directly manage this software, but I can check with the team that does to see if there's a blocker on allowing more lines.
Why do you need so many lines and how many lines would you need, for reference?
Hi @matthewfala
We are creating cloudwatch log group per application and there are more than 20 apps, therefore, there are a lot of lines.
We also raised a support ticket with AWS and they informed us this can be fixed only by reducing characters.
The limitation comes because the configmap is passed to the Fargate Container as overrides parameter and the character limit for "overrides"is 8192 as mentioned here This is a hard limit that cannot be increased
Is there any update to this @jeraldsm
How did you solved this? I am experiencing the same
When we try to add 20 or more outputs to the
aws-logging
ConfigMap, then we get the below error and the config map fails to update.admission webhook "0500-amazon-eks-fargate-configmaps-admission.amazonaws.com" denied the request: Config map has too many chars.
Can I get some help to resolve this issue ?