Introducing impersonation to integrate authentication with cloud-managed clusters
It’s very popular to use managed Kubernetes services from cloud vendors such as Google, Amazon, Microsoft, and DigitalOcean (among many others).
When it comes to these services, they are generally very quick to get up and running, and they all share a common thread: they mostly don’t support OpenID Connect (Amazon’s EKS does support OpenID Connect now, but the cluster must be running on a public network and have a commercially signed TLS certificate).
Earlier in this chapter, we talked about how Kubernetes supports custom authentication solutions through webhooks and that you should never, ever, use this approach unless you are a public cloud provider or some other host of Kubernetes systems. It turns out that pretty much every cloud vendor has its own approach to using these webhooks that uses its own identity and access management implementations. In that case, why not...
