Skip to content
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

Use Unix domain socket for the upstream #199

Open
alebedev87 opened this issue Sep 20, 2022 · 2 comments
Open

Use Unix domain socket for the upstream #199

alebedev87 opened this issue Sep 20, 2022 · 2 comments

Comments

@alebedev87
Copy link

Currently the upstream can only be an URL to an http(s) endpoint which is bound to a network address and port. This would be nice to have a dedicated flag for the upstream which exposes a unix domain socket. The implementation would probably be quite simple: dedicated Dial function with unix as network argument in the transport.
The use case in which this can be useful: PODs which use hostnetwork - to minimize the number of ports occupied on the host.

@alebedev87 alebedev87 changed the title Flag to use Unix domain socket for the upstream Use Unix domain socket for the upstream Sep 20, 2022
@ibihim
Copy link
Collaborator

ibihim commented Jan 17, 2023

Hi, @alebedev87. We are not eager to push for new features, until we get the repository accepted into k8s/sig-auth.

@ibihim
Copy link
Collaborator

ibihim commented Jan 19, 2023

@alebedev87, I synced with the stakeholders and we would like to pause any new feature as long as we don't get accepted by k8s' sig-auth. I would keep this kind of open and come up with some "Backlog" label or so, so we don't forget about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants