Joe Julian

I'm sure folks would be happy to take a look at a PR for this.

No, you're good. It needs to be reviewed by a core maintainer. I've added it to a milestone so it'll either get reviewed by that milestone deadline, or they'll bump...

This would need to be behind a flag as it changes the output which may break automation that relies on current behavior.

If it was me, I'd just create the PR. The core maintainers are all very busy people and giving them the fewest tasks possible usually gets the best results.

@helm/helm-org-maintainers Can you please move this issue to helm-www for the documentation change?

/reopen We just encountered a customer that needs this, too. It could be done through templating in [cmd/clusterctl/client/repository.NewComponents](https://github.com/kubernetes-sigs/cluster-api/blob/5756be13affef606b6683c2c413f0987c1f0e451/cmd/clusterctl/client/repository/components.go#L195) with an option that contains the values for https_proxy, http_proxy, and no_proxy.

@fabriziopandini I don't remember what we did (and I don't work there anymore so I can't go back and check).

> Sounds like we have at least 3 options, in order from "least work required" to "most work required" from our users: > > 1. Include these env variables in...

I've never been a fan of adding the complexity of templating to cluster-api a la ClusterClass, but the community felt the return was worth it. Embracing that change; I'm not...

I don't think you can add generalized proxy support. There's no standard.