| ▲ | breakwaterlabs an hour ago | |
> Human approval doesn’t scale to developers creating and deprecating testing databases, Kubernetes clusters, and CI runners at will. Service (or gMSA) accounts handle this, and auth-integrated reverse proxies can move parts of the problem into a more tractable place. I feel like the article also conveniently forgets that kerberos/ldap backends for SSO systems are extremely common, and solve this. > In Kubernetes, each pod gets a service account token, which allows it to assert its identity within the cluster. How is this qualitatively different than onboarding a new computer object or gMSA entitlement in AD? The problems that the blog asserts affect AD (how to onboard and delegate access and trust) are inherent in any sufficiently robust identity implementation. | ||