Kubernetes has an interesting access control model that goes above and beyond standard access control. For your microservices, it provides the troika of authentication, authorization, and admission. You're probably familiar with authentication (who is calling?) and authorization (what is the caller allowed to do?). Admission is not as common. It can be used for a more dynamic situation where a request may be rejected, even if the caller is properly authenticated and authorized.
Controlling access with authentication, authorization, and admission
Authenticating microservices
Service accounts and RBAC are a good solution to manage identity and access for Kubernetes objects. However, in a microservice architecture, there...
