You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: