-
Notifications
You must be signed in to change notification settings - Fork 187
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
Reuse transport for Helm downloads #590
Conversation
Initial tests on source controller shows that the behaviour is still the same. After 20 minutes running: ghcr.io/fluxcd/source-controller:v0.21.2 To fix #578 we will have to manage the transport lifecycle and send it across to the helm getter. |
ec93675
to
822c860
Compare
b47d573
to
260637b
Compare
This commit updates to a version of Helm 3.8.0, with patches applied to deal with memory leak and HTTP transport issues. The latter being described in #578. Signed-off-by: Hidde Beydals <hello@hidde.co>
Reuses the same transport across different helm chart downloads, whilst resetting the tlsconfig to avoid cross-contamination. Crypto material is now only processed in-memory and does not touch the disk. Signed-off-by: Paulo Gomes <paulo.gomes@weave.works>
Signed-off-by: Paulo Gomes <paulo.gomes@weave.works>
Signed-off-by: Paulo Gomes <paulo.gomes@weave.works>
632545d
to
f63681f
Compare
This looks good to me, great work @pjbgf 🙇 Blocked by GitHub to stamp it as I initialized the PR, but someone else can probably work the magic. |
Signed-off-by: Paulo Gomes <paulo.gomes@weave.works>
bb816d9
to
7d61553
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This commit updates to a version of Helm 3.8.0, with patches applied to
deal with memory leak and HTTP transport issues. The latter being
described in #578.
Potentially fixes #578