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.
I have an AWS cluster with EC2 and fargate nodes. When i deploy the prometheus stack chart it tries to deploy a node exporter daemon set in all the nodes, even in fargate nodes, which are serverless, so it causes that some pods stay Pending.
Describe the solution you'd like
Add the node selector or affinity tag to the value.yml so i can especify in which nodes i want to deploy the node exporters.
Additional context
This is the error that im getting in the fargate nodes:
0/8 nodes are available: 3 Too many pods, 5 node(s) didn't have free ports for the requested pod ports.
This is the affinitt created automatically by the helm chart:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
Is your feature request related to a problem? Please describe.
I have an AWS cluster with EC2 and fargate nodes. When i deploy the prometheus stack chart it tries to deploy a node exporter daemon set in all the nodes, even in fargate nodes, which are serverless, so it causes that some pods stay Pending.
Describe the solution you'd like
Add the node selector or affinity tag to the value.yml so i can especify in which nodes i want to deploy the node exporters.
Additional context
The text was updated successfully, but these errors were encountered: