Skip to content

Conversation

@joamaki
Copy link
Contributor

@joamaki joamaki commented Jan 8, 2026

The changes in #62 are incompatible with how jobs are used in the Cilium operator's
leader lifecycle construct. With this change jobs are tied to the lifecycle of the job.Registry which is not what we need
in the operator where we have two lifecycles. We'll need to rethink the design to allow the module-provided job.Group
in the operator to hook into the leader lifecycle instead of the root lifecycle.

As cilium/hive currently cannot be bumped in cilium/cilium let's revert the changes so that we're not blocking
other fixes.

This reverts commit 044838f.

This change was incompatible with how Cilium implemented the operator
leader lifecycle. This change causes jobs that should only start if
elected leader to always be started since "wrong" lifecycle was used.
We'll need to go back to drawingboard here.

Signed-off-by: Jussi Maki <jussi@isovalent.com>
@joamaki joamaki requested a review from a team as a code owner January 8, 2026 10:47
@joamaki joamaki merged commit 97756f6 into main Jan 8, 2026
1 check passed
@joamaki joamaki deleted the pr/joamaki/revert-job-lifecycle branch January 8, 2026 10:49
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.

2 participants