Skip to content

Feature request: Support configuring an HTTP/S proxy for the AWS, Azure and GCP master keys #1837

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.

Sign up for GitHub

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

Jump to bottom
Open
matheuscscp opened this issue Apr 13, 2025 · 0 comments · May be fixed by #1838
Open

Feature request: Support configuring an HTTP/S proxy for the AWS, Azure and GCP master keys #1837

matheuscscp opened this issue Apr 13, 2025 · 0 comments · May be fixed by #1838

Comments

@matheuscscp
Copy link
Contributor

Hi 👋

In CNCF Flux we support configuring an HTTP/S proxy for interacting with cloud providers and external systems across most of our APIs, one of the few APIs that do not support proxy yet is the Kustomization API where we allow users to decrypt SOPS-encrypted secrets with KMS services from the three major cloud providers.

In order to support proxy for the Kustomization API we would like the AWS, Azure and GCP SOPS master keys to support the configuration of an HTTP/S proxy 🙏
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow injecting custom client options for AWS, Azure and GCP matheuscscp/sops
1 participant
@matheuscscp