Kubernetes Security Concepts: Difference between revisions
| Line 48: | Line 48: | ||
[...] | [...] | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==Non-Default Service Accounts== | |||
To use a non-default service account, set <code>spec.serviceAccountName</code> field of the pod manifest. | |||
=Service Account Operations= | =Service Account Operations= | ||
Revision as of 00:35, 10 August 2020
Internal
Transport Security
User Account
Service Account
Processes in containers inside pods can contact the API server, and they need an identity when doing so. A service account provides the identity for processes that run in a the pod. Processes will authenticate using the identity provided by the service account.
By default, in absence of specific configuration, the pods will authenticate as the default service account in the namespace they are running in. A specific service account name can be specified in the pod manifest. Service accounts are rendered in logs using the following pattern: "system:serviceaccount:namespace:account-name (e.g. "system:serviceaccount:blue:default).
TODO: automountServiceAccountToken: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server
Default Service Account
Each namespace comes with a default service account:
apiVersion: v1
kind: ServiceAccount
metadata:
name: default
namespace: default
secrets:
- name: default-token-dddkl
A pod whose service account was not explicitly configured will run with the default service account fo r its namespace:
apiVersion: v1
kind: Pod
spec:
containers:
- name: [...]
[...]
[...]
serviceAccount: default
serviceAccountName: default
[...]
Non-Default Service Accounts
To use a non-default service account, set spec.serviceAccountName field of the pod manifest.