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
Find a way to restrict the number of discovered targets per LB irrespective of the number of nodes that are being added when cortex clustering up. We don't need up to 500 / 2 = 250 node targets. We only require the operator targets.
Possible solutions
Either find an AWS mechanism that allows us to restrict this to a desired list of targets.
Or maybe configuring NLB IP mode via the aws-load-balancer-controller. This may also require setting externalTrafficPolicy to Local, but not sure.
The text was updated successfully, but these errors were encountered:
Description
Find a way to restrict the number of discovered targets per LB irrespective of the number of nodes that are being added when
cortex cluster
ing up. We don't need up to 500 / 2 = 250 node targets. We only require the operator targets.Possible solutions
externalTrafficPolicy
toLocal
, but not sure.The text was updated successfully, but these errors were encountered: