Remove unnecessary tolerations from fluent-bit pods. These tolerations were far too broad and caused scheduling of these pods onto Fargate nodes, where daemonsets aren't supported. Customers can apply their own site-specific tolerations as necessary.
There weren't similar tolerations for the cloudwatch-agent daemonset, so the impact on existing clusters should be only to remove fluent-bit pods from tainted nodes. Again, customers can apply their own specific tolerations if they desire fluent-bit to be rescheduled on tainted nodes.
Fixes #61
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Description of changes:
Remove unnecessary tolerations from fluent-bit pods. These tolerations were far too broad and caused scheduling of these pods onto Fargate nodes, where daemonsets aren't supported. Customers can apply their own site-specific tolerations as necessary.
There weren't similar tolerations for the cloudwatch-agent daemonset, so the impact on existing clusters should be only to remove fluent-bit pods from tainted nodes. Again, customers can apply their own specific tolerations if they desire fluent-bit to be rescheduled on tainted nodes.
Fixes #61
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.