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

Artifact Streaming Support #266

Open
Bryce-Soghigian opened this issue Apr 15, 2024 · 1 comment
Open

Artifact Streaming Support #266

Bryce-Soghigian opened this issue Apr 15, 2024 · 1 comment
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@Bryce-Soghigian
Copy link
Contributor

Bryce-Soghigian commented Apr 15, 2024

Tell us about your request

Users are asking for support for artifact streaming.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

To enable artifact streaming inside of the Karpenter bootstrapping contract, we need to pass it in as a parameter to the CSE Scripts, and include some additional containerd configuration.

Based on this talk, a simple test validating that pulling sagemathinc/cocalc with a quick timeout should ensure that the image pull is faster and that the feature is working correctly.

The screenshot below should also indicate the types of performance improvements in image pull we can see with the feature enabled.

Screenshot 2024-04-02 at 10 37 45 PM

Enabling artifact streaming has a high cost of additional node bootstrapping latency, so until it is baked into the VHD, we will have it as an alpha field in the AKSNodeClass. Once its baked into the VHD and this cost is gone, we will enable artifact streaming by default and remove this AKSNodeClass field.

Are you currently working around this issue?

No available workarounds

Additional Context

No response

Attachments

No response

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@Bryce-Soghigian
Copy link
Contributor Author

cc: @ganeshkumarashok

@Bryce-Soghigian Bryce-Soghigian added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 15, 2024
@Bryce-Soghigian Bryce-Soghigian self-assigned this Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant