Kubernetes namespace default service account
- A default service account is automatically created for each namespace.
kubectl get serviceaccount
NAME SECRETS AGE
default 1 1d
Service accounts can be added when required. Each pod is associated with exactly one service account but multiple pods can use the same service account.
A pod can only use one service account from the same namespace.
Service account are assigned to a pod by specifying the account’s name in the pod manifest. If you don’t assign it explicitly the pod will use the default service account.
The default permissions for a service account don't allow it tolist or modify any resources. The default service account isn't allowed to view cluster state let alone modify it in any way.
By default, the default service account in a namespace has no permissions other than those of an unauthenticated user.
Therefore pods by default can’t even view cluster state. Its up to you to grant them appropriate permissions to do that.
kubectl exec -it test -n foo sh / # curllocalhost:8001/api/v1/namespaces/foo/services { "kind": "Status",
"apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "services is forbidden: User"system:serviceaccount:foo:default" cannot list resource"services" in API group "" in the namespace "foo"", "reason":"Forbidden", "details": {"kind": "services" }, "code": 403
as can be seen above the default service account cannot list services
but when given proper role and role binding like below
apiVersion: rbac.authorization.k8s.io/v1kind: Rolemetadata: creationTimestamp: null name: foo-role namespace: foorules:- apiGroups: - "" resources: - services verbs: - get - listapiVersion: rbac.authorization.k8s.io/v1kind: RoleBindingmetadata: creationTimestamp: null name: test-foo namespace: fooroleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: foo-rolesubjects:- kind: ServiceAccount name: default namespace: foo
now i am able to list the resurce service
kubectl exec -it test -n foo sh/ # curl localhost:8001/api/v1/namespaces/foo/services{ "kind": "ServiceList", "apiVersion": "v1", "metadata": { "selfLink": "/api/v1/namespaces/bar/services", "resourceVersion": "457324" }, "items": []
Giving all your service accounts the
clusteradmin
ClusterRole is abad idea. It is best to give everyone only the permissions they need to do their job and not a single permission more.It’s a good idea to create a specific service account for each podand then associate it with a tailor-made role or a ClusterRole through aRoleBinding.
If one of your pods only needs to read pods while the other also needs to modify them then create two different service accounts and make those pods use them by specifying the
serviceaccountName
property in thepod spec.
You can refer the below link for an in-depth explanation.
Service account example with roles
You can check kubectl explain serviceaccount.automountServiceAccountToken
and edit the service account
kubectl edit serviceaccount default -o yaml
apiVersion: v1automountServiceAccountToken: falsekind: ServiceAccountmetadata: creationTimestamp: 2018-10-14T08:26:37Z name: default namespace: default resourceVersion: "459688" selfLink: /api/v1/namespaces/default/serviceaccounts/default uid: de71e624-cf8a-11e8-abce-0642c77524e8secrets:- name: default-token-q66j4
Once this change is done whichever pod you spawn doesn't have a serviceaccount token as can be seen below.
kubectl exec tp -it bashroot@tp:/# cd /var/run/secrets/kubernetes.io/serviceaccountbash: cd: /var/run/secrets/kubernetes.io/serviceaccount: No such file or directory
An application/deployment can run with a service account other than default
by specifying it in the serviceAccountName
field of a deployment configuration.
What I service account, or any other user, can do is determined by the roles it is given (bound to) - see roleBindings or clusterRoleBindings; the verbs are per a role's apiGroups
and resources
under the rules
definitions.
The default
service account doesn't seem to be given any roles by default. It is possible to grant a role to the default
service account as described in #2 here.
According to this, "...In version 1.6+, you can opt out of automounting API credentials for a service account by setting automountServiceAccountToken: false
on the service account".
HTH