Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Ability to configure helm chart http proxy via CRs #377

Closed
seaneagan opened this issue Apr 15, 2020 · 1 comment
Closed

Ability to configure helm chart http proxy via CRs #377

seaneagan opened this issue Apr 15, 2020 · 1 comment
Labels
blocked needs validation In need of validation before further action enhancement New feature or request

Comments

@seaneagan
Copy link
Contributor

Describe the feature

Configuring http_proxy / no_proxy env vars can be difficult when some charts need to go through a proxy and some don't, for example when using internal and external helm/git repos. It would be nice to be able to configure the proxy via a CRD field, either underneath the HelmRelease chart field , or in whatever new CRDs come out of #142.

Expected behavior

The CRD based configuration would take precedence over any proxy environment variables.

@seaneagan seaneagan added blocked needs validation In need of validation before further action enhancement New feature or request labels Apr 15, 2020
@kingdonb
Copy link
Member

kingdonb commented Sep 2, 2022

Sorry if your issue remains unresolved. The Helm Operator is in maintenance mode, we recommend everybody upgrades to Flux v2 and Helm Controller.

A new release of Helm Operator is out this week, 1.4.4.

We will continue to support Helm Operator in maintenance mode for an indefinite period of time, and eventually archive this repository.

Please be aware that Flux v2 has a vibrant and active developer community who are actively working through minor releases and delivering new features on the way to General Availability for Flux v2.

In the mean time, this repo will still be monitored, but support is basically limited to migration issues only. I will have to close many issues today without reading them all in detail because of time constraints. If your issue is very important, you are welcome to reopen it, but due to staleness of all issues at this point a new report is more likely to be in order. Please open another issue if you have unresolved problems that prevent your migration in the appropriate Flux v2 repo.

Helm Operator releases will continue as possible for a limited time, as a courtesy for those who still cannot migrate yet, but these are strongly not recommended for ongoing production use as our strict adherence to semver backward compatibility guarantees limit many dependencies and we can only upgrade them so far without breaking compatibility. So there are likely known CVEs that cannot be resolved.

We recommend upgrading to Flux v2 which is actively maintained ASAP.

I am going to go ahead and close every issue at once today,
Thanks for participating in Helm Operator and Flux! 💚 💙

@kingdonb kingdonb closed this as completed Sep 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked needs validation In need of validation before further action enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants