Pushing with kaniko is slow #2751
Labels
area/performance
issues related to kaniko performance enhancement
issue/http2
kind/friction
priority/p2
High impact feature/bug. Will get a lot of users happy
Actual behavior
Pushing large images (e.g 5Gb) with kaniko to some https registries (e.g ecr, quay or gitlab contianer registry) has been identified to be quite slow when using kaniko . After some preliminary investigation (in https://gitlab.com/gitlab-org/gitlab/-/issues/241996 )it appears the slowness comes from the issue mentioned in golang/go#47840 and is related to the http/2 implementation of
net/httpBecause of the slowness caused by golang/go#47840 docker and buildx registry clients have opted to only push on http/1.1 connection. see: moby/buildkit#1420
A few issues have been raised on (go-containerregistry) which kaniko uses that alludes to a similar http2 bottleneck:
Expected behavior
Pushing a 5Gb layer using kaniko to gitlab contianer registry, ecr or quay should not take > 30mins on arguably fast internet connections
To Reproduce
Steps to reproduce the behavior:
Additional Information
Triage Notes for the Maintainers
--cacheflagThe text was updated successfully, but these errors were encountered: