Repository navigation
etcd-operator: from StatefulSets to a custom operator #123
nwnt
started this conversation in
Maintainer Summit NA 2026
Replies: 2 comments
|
NOTE: this session cannot be scheduled opposite the SIG-etcd meeting, which happens at 2:20pm, as it involves several of the same people. |
0 replies
|
This session has been scheduled for 4:00PM: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/features-add-ons/maintainer-summit/?id=1318486#schedule Thank you for leading this discussion! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Topic
etcd-operator: from StatefulSets to a customer operator
What projects are involved?
wg-etcd-operator, sig-apps
Description
Kubernetes StatefulSet was created to support databases and cloud filesystems. The new etcd-operator project started out on StatefulSet, but found itself needing to move to creating a custom controller instead, as have a majority of database operators.
We will explain the roadblocks that compelled this change, and breifly review how database operators are dealing with pod management across the ecosystem. We'll discuss some what etcd-operator had to do to replace the StatefulSet functionality. And then we'll share the improvements that are coming to StatefulSet that might make creating a custom controller unnecessary in the future.
Session lead contact information
Nont Thanonchai @nont
Marciej Szulik @soltysh
Josh Berkus @jberkus
All reactions