Skip to content

Update network-services-operator to be multi-cluster aware #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
joshlreese opened this issue Mar 7, 2025 · 0 comments · Fixed by #9
Closed

Update network-services-operator to be multi-cluster aware #7

joshlreese opened this issue Mar 7, 2025 · 0 comments · Fixed by #9
Assignees

Comments

@joshlreese
Copy link
Contributor

Today, an instance of the operator is deployed for each Datum Project to manage only resources for that project. In an effort to make this more efficient, we would like to make the operator multi-cluster aware, allowing a single instance to serve multiple projects.

A substantial amount of effort has been put into bringing this capability directly into the controller-runtime library, tracked in kubernetes-sigs/controller-runtime#2746, which has evolved into the multicluster-runtime library.

We should explore using this library and participating in its evolution, as the project goals are aligned with our own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant