This content originally appeared on DEV Community and was authored by Sina Tavakkol

Day 25/40

Kubernetes Service Account - RBAC Continued

Video Link
@piyushsachdeva
Git Repository
My Git Repo

In this section, we are looking at service account

What are service accounts?

A service account is a type of non-human account that, in Kubernetes, provides a distinct identity in a Kubernetes cluster. Application Pods, system components, and entities inside and outside the cluster can use a specific ServiceAccount's credentials to identify as that ServiceAccount. This identity is useful in various situations, including authenticating to the API server or implementing identity-based security policies.
source

(Photo from the video)

When you create a cluster, Kubernetes automatically creates a ServiceAccount object named default for every namespace in your cluster.
source

root@localhost:~# kubectl get sa
NAME      SECRETS   AGE
default   0         27d
root@localhost:~# kubectl describe sa default
Name:                default
Namespace:           default
Labels:              <none>
Annotations:         <none>
Image pull secrets:  <none>
Mountable secrets:   <none>
Tokens:              <none>
Events:              <none>
root@localhost:~# kubectl get sa default -o yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  creationTimestamp: "2024-07-01T16:17:24Z"
  name: default
  namespace: default
  resourceVersion: "392"
  uid: 4c64b284-e8c3-4e70-a67e-cb7c0d5a379e

Create a service account

root@localhost:~# kubectl create sa build-sa
serviceaccount/build-sa created
root@localhost:~# kubectl describe sa build-sa
Name:                build-sa
Namespace:           default
Labels:              <none>
Annotations:         <none>
Image pull secrets:  <none>
Mountable secrets:   <none>
Tokens:              <none>
Events:              <none>

Manually create a long-lived API token for a ServiceAccount

If you want to obtain an API token for a ServiceAccount, you create a new Secret with a special annotation, kubernetes.io/service-account.name.
source

Service account token

apiVersion: v1
kind: Secret
metadata:
  name: build-robot-secret
  annotations:
    kubernetes.io/service-account.name: build-sa
type: kubernetes.io/service-account-token

root@localhost:~# kubectl apply -f day25-secret.yaml
secret/build-robot-secret created
root@localhost:~# kubectl get secret
NAME                 TYPE                                  DATA   AGE
build-robot-secret   kubernetes.io/service-account-token   3      8s
root@localhost:~# kubectl describe secret build-robot-secret
Name:         build-robot-secret
Namespace:    default
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: build-sa
              kubernetes.io/service-account.uid: 2f2bbf57-41ad-4be1-a4b6-618a093edd45

Type:  kubernetes.io/service-account-token

Data
====
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6ImEwemh... R4gFq5INlcdOrbF-6yQEe9fz6n2znYoSmX3Qi-BKX3HL8dMbQ2McvXXTNbcr9T8Cnw3Sa2uJA2uoD8QKmzBKjzSSeac8ymUvq0kYgbIIC4ITdtZCA26hD54Hds3i92uoQ245Vfh9miW_YVHtkVgL9tCjrKJRfkEYEfd2H_Eijq-W6HPePUC7m1lvIviYZr1IcCfUDY8jHt8XwIVPs6JwzQnkirRWq-3bylmvNNR1W7FqwwADjv581mmwHSY4KoDpjM0T_a-kJCN8ufLI_m6o12Tw
ca.crt:     1107 bytes
namespace:  7 bytes

Add ImagePullSecrets to a service account

Let's say we have a private image repository and need to have a service account to pull images from it. That's where we use ImagePullSecret to authentication and authorization for our private registry.

Sample source

apiVersion: v1
kind: Pod
metadata:
  name: foo
  namespace: awesomeapps
spec:
  containers:
    - name: foo
      image: janedoe/awesomeapp:v1
  imagePullSecrets:
    - name: myregistrykey

This needs to be done for each pod that is using a private registry.

Creating a Secret with a Docker config

source

kubectl create secret docker-registry <name> \
  --docker-server=DOCKER_REGISTRY_SERVER \
  --docker-username=DOCKER_USER \
  --docker-password=DOCKER_PASSWORD \
  --docker-email=DOCKER_EMAIL

After you made those changes, the edited ServiceAccount looks something like this:

apiVersion: v1
kind: ServiceAccount
metadata:
  creationTimestamp: 2021-07-07T22:02:39Z
  name: default
  namespace: default
  uid: 052fb0f4-3d50-11e5-b066-42010af0d7b6
imagePullSecrets:
  - name: myregistrykey

Check the permission of the service account

root@localhost:~# kubectl get pods --as build-sa
Error from server (Forbidden): pods is forbidden: User "build-sa" cannot list resource "pods" in API group "" in the namespace "default"
root@localhost:~# kubectl auth can-i get pods --as build-sa
no

So we need to have role and rolebinding for that.

root@localhost:~# kubectl create role build-role --verb=list,get,watch --resource=pod
role.rbac.authorization.k8s.io/build-role created
root@localhost:~# kubectl create rolebinding build-rolebinding --role=build-role --user=build-sa
rolebinding.rbac.authorization.k8s.io/build-rolebinding created
root@localhost:~# kubectl get role,rolebinding
NAME                                        CREATED AT
role.rbac.authorization.k8s.io/build-role   2024-07-29T15:09:45Z
role.rbac.authorization.k8s.io/developer    2024-07-28T19:20:16Z
role.rbac.authorization.k8s.io/pod-reader   2024-07-24T16:27:15Z

NAME                                                      ROLE              AGE
rolebinding.rbac.authorization.k8s.io/build-rolebinding   Role/build-role   12s
rolebinding.rbac.authorization.k8s.io/developer-role      Role/developer    19h
rolebinding.rbac.authorization.k8s.io/read-pods           Role/pod-reader   4d22h

Let's check the permission

root@localhost:~# kubectl auth can-i get pods --as build-sa
yes
root@localhost:~# kubectl get pods --as build-sa
NAME          READY   STATUS    RESTARTS   AGE
nginx-pod-3   1/1     Running   0          4d22h

Check service account data in pod details

root@localhost:~# kubectl describe pod nginx-pod-3
Name:             nginx-pod-3
Namespace:        default
Priority:         0
Service Account:  default

...

    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-gksff (ro)

...

root@localhost:~# kubectl exec -it nginx-pod-3 -- bash
root@nginx-pod-3:/# ls -lh /var/run/secrets/kubernetes.io/serviceaccount/
total 0
lrwxrwxrwx 1 root root 13 Jul 24 17:04 ca.crt -> ..data/ca.crt
lrwxrwxrwx 1 root root 16 Jul 24 17:04 namespace -> ..data/namespace
lrwxrwxrwx 1 root root 12 Jul 24 17:04 token -> ..data/token

This content originally appeared on DEV Community and was authored by Sina Tavakkol

Print Share Comment Cite Upload Translate Updates

APA

Sina Tavakkol | Sciencx (2024-08-01T14:11:43+00:00) 40 Days Of Kubernetes (25/40). Retrieved from https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/

MLA

" » 40 Days Of Kubernetes (25/40)." Sina Tavakkol | Sciencx - Thursday August 1, 2024, https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/

HARVARD

Sina Tavakkol | Sciencx Thursday August 1, 2024 » 40 Days Of Kubernetes (25/40)., viewed ,<https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/>

VANCOUVER

Sina Tavakkol | Sciencx - » 40 Days Of Kubernetes (25/40). [Internet]. [Accessed ]. Available from: https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/

CHICAGO

" » 40 Days Of Kubernetes (25/40)." Sina Tavakkol | Sciencx - Accessed . https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/

IEEE

" » 40 Days Of Kubernetes (25/40)." Sina Tavakkol | Sciencx [Online]. Available: https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/. [Accessed: ]

rf:citation

» 40 Days Of Kubernetes (25/40) | Sina Tavakkol | Sciencx | https://www.scien.cx/2024/08/01/40-days-of-kubernetes-25-40/ |

Please log in to upload a file.

There are no updates yet.
Click the Upload button above to add an update.

You must be logged in to translate posts. Please log in or register.