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.
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
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.
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