[Feature] Simplify reconciliation by simplifying claim logic for StatefulSet, Service and ConfigMap based on Etcd resource name #186
Labels
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
status/closed
Issue is closed (either delivered or triaged)
Feature (What you would like to be added):
The reconciliation flow of
etcd-druid
includes claiming from potentially multiple pre-existingStatefulSet
,Service
andConfigMap
objects if they exist. This is done by selecting the objects based onspec.selector
in theEtcd
resource, claiming one of the matching objects (if any) and deleting the rest of the objects (if any). If no matching objects are found then a new object is created.The logic of claiming from multiple pre-existing objects objects based on
spec.selector
was done because of the following reasons.etcd-druid
was introduced. I.e. adopting objects created from the time beforeetcd-druid
was introduced minimised and simplified clean up.StatefulSet
for all the members of an ETCD cluster. Another alternative of using oneStatefulSet
for each member of an ETCD cluster was still open at that time.Now that the migration scenario as well as the multi-node design don't need the functionality of claiming from multiple pre-existing objects, we can simplify the claim logic to just pick the object to be claimed by the same name as the
Etcd
resource . We will still need the claim functionality to mark it as claimed, of course.Motivation (Why is this needed?):
Approach/Hint to the implement solution (optional):
The text was updated successfully, but these errors were encountered: