Skip to content

feat: operator-owner handoff for blue/green operator rollout - #373

Closed
garrettthomaskth wants to merge 1 commit into
mainfrom
feat/operator-owner-handoff
Closed

garrettthomaskth wants to merge 1 commit into
mainfrom
feat/operator-owner-handoff

Conversation

@garrettthomaskth

@garrettthomaskth garrettthomaskth commented Oct 20, 2026 •

Copy link
Copy Markdown

Why

What

Related Issues

Fixes #
Related to #

Lets a cluster be reconciled by one operator instance at a time during a
blue/green operator rollout, driven by the clickhouse.com/operator-owner
and clickhouse.com/desired-operator-owner labels and the
clickhouse.com/operator-owner-claim annotation that
data-plane-management's admin API sets
(ClickHouse/data-plane-application#42687, #43331, #43695):

- an operator instance that is not the operator-owner stops reconciling
  Services, so two operator instances never fight over the same Service
- an instance that is the desired-operator-owner but not yet the owner
  writes a claim annotation
- the current owner, seeing a different desired owner and a matching
  claim, moves operator-owner to the claimant
- a cluster with no operator-owner label is reconciled as before by every
  instance, so this rolls out ahead of the migration itself

OperatorOwnerID defaults to the operator's build version, matching the
identifier the rollout workflow already uses for -desired-owner.
@GrigoryPervakov
GrigoryPervakov deleted the feat/operator-owner-handoff branch October 20, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant