[aws-for-fluent-bit] Adding common tollerations to aws-for-fluent-bit daemonset
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
In my Kubernetes cluster, almost the nodes are added taints, when I install `aws-for-fluent-bit` it was just installed on 2 nodes which are not tainted.
```
⚡ $ ks get daemonset
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
aws-for-fluent-bit 2 2 2 2 2 29m
```
The `aws-for-fluent-bit` chart should have default toleration to support deploy the pod on all nodes, for example.
```
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
- effect: NoExecute
operator: Exists
```
Contributor guide
Research direction
Find the aws-for-fluent-bit chart and inspect its DaemonSet template and values. Render or install the chart to confirm the default tolerations are present and allow scheduling on tainted nodes; done means the rendered DaemonSet includes the requested NoSchedule and NoExecute tolerations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100