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

Feature Request: Reuse Knative eventing/job container #6131

Open
milo157 opened this issue Oct 2, 2024 · 2 comments
Open

Feature Request: Reuse Knative eventing/job container #6131

milo157 opened this issue Oct 2, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@milo157
Copy link

milo157 commented Oct 2, 2024

What is changing? (Please include as many details as possible.)

For long running tasks, you can't reuse containers. It seems to be because knative eventing creates jobs not pods. It would be great to reuse event containers (whether jobs or pods) instead of creating new jobs for a task.

The use case is for jobs that have a high initialisation time eg: Loading LLM's to process data that take minutes to load into GPU Memory and that take a long time to process

@milo157 milo157 changed the title Reuse Knative eventing/job container Feature Request: Reuse Knative eventing/job container Oct 2, 2024
@skonto
Copy link
Contributor

skonto commented Nov 6, 2024

hi @milo157 probably you should open this at the knative/eventing project.
cc @pierDipi @creydr

Copy link

github-actions bot commented Feb 5, 2025

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants