Repository navigation
Commit 9f6fdd7
committed
docs(etcd): update the affinity notes for the hard member spread
The affinity description and the comment above the affinity block
explained the soft default by a member that would stay Pending on its
node-local volume. Now that the spread is DoNotSchedule by default, the
spread keeps such a member Pending as well, once its node holds another
member and some other node holds none. Both texts now explain the soft
default by what is left, that a required rule forbids two members on
one node even when every node has one, and state the node-local case
for both rules.
The description also says that the operator copies affinity into each
EtcdMember when it creates it, so a recreated Pod keeps the rule its
member was created with. README, values.schema.json and the
ApplicationDefinition are regenerated from it.
Assisted-by: LLM
Signed-off-by: Yan Bondarenko <[email protected]>1 parent f1f30b3 commit 9f6fdd7
5 files changed
Lines changed: 22 additions & 18 deletions
File tree
- packages
- extra/etcd
- templates
- system/etcd-rd/cozyrds
0 commit comments