[EKS] [request]: Set priorityClassName for cloudwatch addon

[voidlily]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Cloudwatch addon for EKS doesn't set priorityClassName or have a configuration option to allow it to be set.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I tried to deploy the Cloudwatch addon to my cluster and several nodes weren't able to schedule the agent or fluent-bit daemonset pods due to the nodes being full. This would be solved by adding priorityClassName: system-node-critical on the daemonset pod templates to allow these pods to preempt.

Are you currently working around this issue?
Setting the priorityClassName manually currently, but not sustainable when automating cluster deployments via terraform.

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

[voidlily]

see also aws-observability/helm-charts#70 for an open PR on the helm chart version of this addon (but as of time of writing only sets priorityClassName on fluent-bit, not yet on the cloudwatch agent daemonset)