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
Is your feature request related to a problem? Please describe.
There are use-cases wherein you might need to schedule sumologic collector into a tainted nodepool atm all the other components are being scheduled correctly into tainted nodepools but not the sumologic-setup job which means if there are no nodepools in your cluster with no taints the setup job will never be scheduled thus setup will never proceed.
Describe the solution you'd like
Ability to define tolerations and affinity in the setup job.
Describe alternatives you've considered
Temporarily spinup a nodepool with a single node with no taint just for setup to proceed and tear it down after setup which breaks our preffered automation way and is kinda wasteful.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are use-cases wherein you might need to schedule sumologic collector into a tainted nodepool atm all the other components are being scheduled correctly into tainted nodepools but not the sumologic-setup job which means if there are no nodepools in your cluster with no taints the setup job will never be scheduled thus setup will never proceed.
Describe the solution you'd like
Ability to define tolerations and affinity in the setup job.
Describe alternatives you've considered
Temporarily spinup a nodepool with a single node with no taint just for setup to proceed and tear it down after setup which breaks our preffered automation way and is kinda wasteful.
The text was updated successfully, but these errors were encountered: