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
The target allocator now has two methods of allocation (least-weighted, and consistent-hashing) the next strategy will be a composite strategy that will only assign targets post relabeling. All of these strategies have some amount of configuration to them, we should allow users of the TA to specify them in the CRD.
This also will allow us to have strategies as typed and not just strings in the CRD. The change will involve passing the spec containing the TA config down to each allocation strategy rather than just a logger as it stands right now.
The target allocator now has two methods of allocation (least-weighted, and consistent-hashing) the next strategy will be a composite strategy that will only assign targets post relabeling. All of these strategies have some amount of configuration to them, we should allow users of the TA to specify them in the CRD.
This also will allow us to have strategies as typed and not just strings in the CRD. The change will involve passing the spec containing the TA config down to each allocation strategy rather than just a logger as it stands right now.
Original discussion here
The text was updated successfully, but these errors were encountered: