Why not an Authenticating Proxy
mikebell90 opened this issue · 2 comments
mikebell90 commented
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 commented
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.