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

Use annotation for setting up resource required for elyra integration #213

Open
harshad16 opened this issue Oct 19, 2023 · 1 comment
Open
Labels
kind/feature New feature

Comments

@harshad16
Copy link
Member

/kind feature

Why you need this feature:
[Is your feature request related to a problem? Please describe in details]

Currently, On ODH notebooks, if a user wants use elyra with the data science pipeline instance. They have to setup the pipeline server first and then setup the workbench on the DS project. The Overhead of setting the Required RBAC and secrets for Elrya to work in Notebook seamlessly to spin up pipelines in data -science pipeline server falls on the ODH Dashboard.

Goal, of the issue, is to find a way to easy out the overhead.

  1. RBAC setup:
    The role-binding, is done by using the service account of the notebook and the role provided by the DSPA.
    We could use an annotation method, where Dashboard instead of creating a RBAC
    just sets an annotation on the notebook. ex: pipeline-role:

using this NBC, can set the RBAC for the workbench, with these the setup and cleanup become more clean.

  1. Secret setup:
    The secret has more moving piece, however this could be something which could be streamlined in same pattern.
@openshift-ci openshift-ci bot added the kind/feature New feature label Oct 19, 2023
@harshad16
Copy link
Member Author

  1. Notify users when a pipeline server is created, about restarting a notebook they want to use.

Questions:
Scenario 1: let's say a user wants to use a notebook that was not restarted on the day of pipeline creation,
and forget about restarting and falling into the trap, what to do in this scenario?
idea: Add a label and remove it when restarted.

Scenario 2: let's say, NBC restarts all the notebooks with elyra on the DS project.
Consequence: Fall into resource limitations, user data loss due to restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature
Projects
Status: No status
Status: No status
Status: 🔖Todo
Development

No branches or pull requests

1 participant