Skip to content
This repository has been archived by the owner on May 17, 2024. It is now read-only.

Why not an Authenticating Proxy #152

Open
mikebell90 opened this issue May 9, 2020 · 2 comments
Open

Why not an Authenticating Proxy #152

mikebell90 opened this issue May 9, 2020 · 2 comments

Comments

@mikebell90
Copy link

Forgive me this ignorant question as I'm a relative Kubernetes n00b.

Why is this not implemented as an Authenticating Proxy instead of the way it is? Wouldn't that be cleaner and avoid the whole impersonation thing?

Feels cleaner to me, so I'm probably missing a crucial detail?

@JoshVanL
Copy link
Contributor

Hello!

The reason for this is when using Kubernetes platforms (GKE, EKS...) where there is no access to the API server CLI flags and so can't be configured. This means that functionality needs to be put outside of the control plane, which makes using impersonation a requirement.

@krmayankk
Copy link

@JoshVanL i see a big warning at the top of the readme for this project. What makes this project not secure enough ?Is there a list of things listed somewhere which are known issues or things we need to worry about from security perspective ?

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

No branches or pull requests

3 participants