Support downstream proxy for connections going to cluster-external resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Feature Request
Support for downstream proxies required to access cluster-external resources
What problem are you trying to solve?
In our cluster we can't just connect to URLs outside of the cluster but need to route them through a security proxy.
How should the problem be solved?
Allow specification of downstream proxy (host and port) for external connections.
I guess the best place for this would be a service profile.
What do you want to happen? Add any considered drawbacks.
When a request is targeted to a configured (cluster-external) host, the request is sent to the configured downstream proxy instead of directly trying to connect to the host.
Any alternatives you've considered?
Is there another way to solve this problem that isn't as good a solution?
How would users interact with this feature?
If you can, explain how users will be able to use this. Maybe some sample CLI
output?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing service-profile handling and the external-connection path; done means a configured host and port route matching cluster-external requests through the downstream proxy instead of connecting directly.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100