Kubernetes Security Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
=Role Based Access Control (RBAC)= | =Role Based Access Control (RBAC)= | ||
In Kubernetes, granting a role to an application-specific service account is a best practice to ensure that the application is operated in a specified scope. <font color=darkgray>TODO: https://kubernetes.io/docs/reference/access-authn-authz/rbac/#service-account-permissions</font> | In Kubernetes, granting a role to an application-specific service account is a best practice to ensure that the application is operated in a specified scope. | ||
<font color=darkgray>TODO: | |||
* https://kubernetes.io/docs/reference/access-authn-authz/rbac/#service-account-permissions | |||
* https://docs.bitnami.com/kubernetes/how-to/configure-rbac-in-your-kubernetes-cluster/</font> | |||
Revision as of 18:49, 28 August 2019
Internal
Transport Security
Service Account
A service account provides an identity for processes that run in a Pod.
TODO:
- https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
- https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/
Role Based Access Control (RBAC)
In Kubernetes, granting a role to an application-specific service account is a best practice to ensure that the application is operated in a specified scope.
TODO: