Skip to content

feat: Allow scoping operator installation to specific namespace #719

@ekampf

Description

@ekampf

What is missing?
Right now operator can only run in "cluster mode" and there's no ability to scope it to specific namespace.
This use case is mainly for testing and non-production use cases.

Why do we need it?
We’re supporting testing scenarios where multiple engineers each have their own namespace, allowing them to independently deploy the operator and run their workflows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions