Add cluster size indicator label to etcd pods #877
Labels
area/ops-productivity
Operator productivity related (how to improve operations)
area/usability
Usability related
kind/enhancement
Enhancement, improvement, extension
Comments
gardener-robot
added
area/ops-productivity
|
can you also add what is the gap that you have seen which causes issues when using kupid/kyverno? Also can you adjust your description as these are not really schedulers. |
unmarshall
added a commit
to unmarshall/etcd-druid
that referenced
this issue
Sep 30, 2024
unmarshall
added a commit
to unmarshall/etcd-druid
that referenced
this issue
Oct 23, 2024
Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 Added use-etcd-wrapper cli arg for etcdbr container
unmarshall
added a commit
to unmarshall/etcd-druid
that referenced
this issue
Oct 23, 2024
Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 Added use-etcd-wrapper cli arg for etcdbr container
unmarshall
added a commit
to unmarshall/etcd-druid
that referenced
this issue
Oct 23, 2024
Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 Added use-etcd-wrapper cli arg for etcdbr container
shreyas-s-rao
pushed a commit
that referenced
this issue
Oct 23, 2024
…client and peer communication (#883) * fixes #881, #877 * Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 * Added use-etcd-wrapper cli arg for etcdbr container * removed etcd-cluster-size label to be added later with ability to restore while keep etcd.spec.replicas > 1
shreyas-s-rao
pushed a commit
to shreyas-s-rao/etcd-druid
that referenced
this issue
Oct 23, 2024
…client and peer communication (gardener#883) * fixes gardener#881, gardener#877 * Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 * Added use-etcd-wrapper cli arg for etcdbr container * removed etcd-cluster-size label to be added later with ability to restore while keep etcd.spec.replicas > 1
|
The label was not added in #883 , as it breaks certain scheduling decisions when topology spread constraints are orthogonally added to the statefulset without going through the Etcd spec, especially during the scale-up scenario from 1 replica to 3 replicas. This is because, the single-replica pod will have |
shreyas-s-rao
added a commit
that referenced
this issue
Oct 23, 2024
…client and peer communication (#883) (#894) * fixes #881, #877 * Added ability to handle unknown CLI args to allow switching between v0.22 and v0.23 * Added use-etcd-wrapper cli arg for etcdbr container * removed etcd-cluster-size label to be added later with ability to restore while keep etcd.spec.replicas > 1 Co-authored-by: Madhav Bhargava <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to categorize this issue?
/area usability ops-productivity
/kind enhancement
What would you like to be added:
Druid should add a new label to etcd pods to indicate the cluster size, or whether it's part of a single-node or multi-node cluster.
Why is this needed:
This allows for better scheduling decisions by orthogonal schedulers like kupid or kyverno. The label can be named
druid.gardener.cloud/etcd-cluster-size: Nfor example.The text was updated successfully, but these errors were encountered: