-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Enhancement request: low-latency containers #1446
Comments
@stevef1uk: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @stevef1uk, issues in this repo are created after consultation with the SIG that should own the enhancement. In this case, in my opinion, please discuss with @kubernetes/sig-scheduling-feature-requests and/or @kubernetes/sig-scalability-feature-requests first before filing an enhancements issue. Also, according to the guidelines governing on what is an enhancement, the above seems to be a performance improvement which is unlikely an enhancement. More information on when to create an enhancement issue: https://github.com/kubernetes/enhancements#when-to-create-a-new-enhancement-issue |
Closing it for now. Please feel free to reopen after discussion. /close |
@palnabarun: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@stevef1uk - I'm running into the same issue with ArgoWF |
NE-1366: Revisions for set-delete-http-headers EP
Enhancement Description
The ability to start up containers in milliseconds rather than seconds
Responsible SIGs:
?
Justification/ Explanation: I was experimenting with Argo as a more portable option to AWS Step Functions and noticed that the time to execute an Argo workflow on Kubernetes is quite long. This could be due to the time Kubernetes takes to schedule & deploy a Pod to run a container, which is simply the next step in an Argo workflow.
I would like the ability to run containers on Kubernetes in milliseconds rather than seconds. I noticed in this link that the Scheduler has very different SLA expectations: kubernetes/kubernetes#3954
The text was updated successfully, but these errors were encountered: