-
Notifications
You must be signed in to change notification settings - Fork 30
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
WebConsole: allow pipeline configuration and monitoring #939
Labels
Comments
@Karakatiza666 I made this part of next milestone in discussion with @lalithsuresh earlier because he's dependent on it |
Karakatiza666
added a commit
that referenced
this issue
Nov 15, 2023
Signed-off-by: George <bulakh.96@gmail.com>
Karakatiza666
added a commit
that referenced
this issue
Nov 15, 2023
Signed-off-by: George <bulakh.96@gmail.com>
Karakatiza666
added a commit
that referenced
this issue
Nov 17, 2023
Signed-off-by: George <bulakh.96@gmail.com>
Karakatiza666
added a commit
that referenced
this issue
Nov 17, 2023
Signed-off-by: George <bulakh.96@gmail.com>
Karakatiza666
added a commit
that referenced
this issue
Nov 20, 2023
Signed-off-by: George <bulakh.96@gmail.com>
PR is waiting for an additional back-end feature; moving to next milestone |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We currently do not expose a way to configure some key properties of a pipeline, and produce a PipelineConfig entry with defaults.
We'll need the ability to set and monitor some values of a PipelineConfig object from the UI:
workers
resource limits/reservations
: Allow configuring resource requirements for each pipeline #940The text was updated successfully, but these errors were encountered: