Skip to content

Conversation

@mikhail-klimko
Copy link
Contributor

@mikhail-klimko mikhail-klimko commented Nov 4, 2025

What

Adding a debug flag so that the gitops operator can be "disabled" when a developer want's to run a debug version of the operator in a cluster with mirrord. The issue this solves is that when you run the operator via mirrord, the existing operator container still receives cluster resource events so the two operators compete and race each other leading to weird/wrong behaviour. Currently the operator cannot be scaled horizontally.

We need the pod to run so that mirrord can intercept traffic to/from it for the debug instance of the operator.

Why

The mirrord solution for this is to install their operator into the cluster and use their paid version. It doesn't seem worth it for just one component so we came up with this solution.

Notes

Copy link
Contributor

@scme0 scme0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've confirmed this seems to be working well locally

@scme0 scme0 marked this pull request as ready for review November 5, 2025 07:45
@scme0 scme0 requested a review from a team as a code owner November 5, 2025 07:45
@scme0
Copy link
Contributor

scme0 commented Nov 5, 2025

/e2e

@scme0
Copy link
Contributor

scme0 commented Nov 5, 2025

/e2e

@scme0 scme0 merged commit baabd74 into main Nov 5, 2025
5 checks passed
@scme0 scme0 deleted the feat/mirrord-debug branch November 5, 2025 15:46
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.

4 participants