Skip to content
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

Run workflows in provider namespaces #406

Open
grahamia opened this issue Dec 5, 2024 · 1 comment
Open

Run workflows in provider namespaces #406

grahamia opened this issue Dec 5, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@grahamia
Copy link
Contributor

grahamia commented Dec 5, 2024

Is your feature request related to a problem? Please describe.
Currently when and reconciles happen which triggers a workflow to run, i.e. new pipeline resource created the generated workflow runs within the kfp-operator-system namespace. To allow for segregation between providers it should be possible to run the workflows within a provider specific namespace, therefore allowing for separate management of the provider namespaces along with the service account setup therefore making it possible to apply correct security to data access etc between providers.

Describe the solution you'd like
On a KFP Operator user resource being created/updated/deleted and triggering a reconcile it should be possible to set the generated workflow to run within the provider namespace rather than al providers workflows running within the same namespace (kfp-operator-system by default)

Currently all workflows are generated in the configured namespace:

Namespace:    workflows.Config.WorkflowNamespace

in the KfpControllerConfigSpec

This configuration value could be made optional and if not set then the namespace of the provider resource can be used.

KFP Operator service account will need the necessary access permissions to create the resource in the namespace.

@grahamia
Copy link
Contributor Author

grahamia commented Dec 5, 2024

Solution should still allow for simple deployments with all resources etc in the single namespace.

@grahamia grahamia added the enhancement New feature or request label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant