Skip to content

Commit 0f878f0

Browse files
committed
Update changelog
1 parent d6435e3 commit 0f878f0

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

.chloggen/add_fallback_strategy_for_per_node_strategy.yaml

+4-2
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ change_type: 'enhancement'
55
component: target allocator
66

77
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8-
note: Added allocation_fallback_strategy option as fallback strategy for per-node allocation strategy
8+
note: Added allocation_fallback_strategy option as fallback strategy for per-node allocation strategy, can be enabled with feature flag operator.targetallocator.fallbackstrategy
99

1010
# One or more tracking issues related to the change
1111
issues: [3477]
@@ -16,4 +16,6 @@ issues: [3477]
1616
subtext: |
1717
If using per-node allocation strategy, targets that are not attached to a node will not
1818
be allocated. As the per-node strategy is required when running as a daemonset, it is
19-
not possible to assign some targets under a daemonset deployment
19+
not possible to assign some targets under a daemonset deployment.
20+
Feature flag operator.targetallocator.fallbackstrategy has been added and results in consistent-hashing
21+
being used as the fallback allocation strategy for "per-node" only at this time.

0 commit comments

Comments
 (0)