Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[aws-for-fluent-bit] Adding common tollerations to aws-for-fluent-bit daemonset #781

Open
vumdao opened this issue Jul 5, 2022 · 0 comments · May be fixed by #1168
Open

[aws-for-fluent-bit] Adding common tollerations to aws-for-fluent-bit daemonset #781

vumdao opened this issue Jul 5, 2022 · 0 comments · May be fixed by #1168
Labels
enhancement New feature or request

Comments

@vumdao
Copy link

vumdao commented Jul 5, 2022

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           <none>                        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
@vumdao vumdao added the enhancement New feature or request label Jul 5, 2022
@vumdao vumdao changed the title [aws-for-fluent-bit] Adding common tolleration to aws-for-fluent-bit daemonset [aws-for-fluent-bit] Adding common tollerations to aws-for-fluent-bit daemonset Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant