The AWS Observability Helm Charts repository contains Helm charts to provide easy mechanisms to setup the CloudWatch Agent and other collection agents to collect telemetry data such as metrics, logs and traces to send to AWS monitoring services.
Apache License 2.0
10
stars
17
forks
source link
should be able to set priorityClassName for fluent #54
My observation is unless I can set priorityClassName: system-node-critical for the fluent-bit daemon set, the cluster can end up in a broken state where it can't start fluent-bit on a node because there are not enough resources on a given node, but it will not kick off any of the pods that are consuming the resources either.
By setting this priority, it will kick off some of the less important pods, which will be rescheduled on other nodes, and fluent-bit is allowed to run.
But this chart doesn't appear to allow setting that value.
My observation is unless I can set
priorityClassName: system-node-critical
for the fluent-bit daemon set, the cluster can end up in a broken state where it can't start fluent-bit on a node because there are not enough resources on a given node, but it will not kick off any of the pods that are consuming the resources either.By setting this priority, it will kick off some of the less important pods, which will be rescheduled on other nodes, and fluent-bit is allowed to run.
But this chart doesn't appear to allow setting that value.