Post

[Kubernetes] Role, Clusterrole, Binding

πŸ“Œ λ“€μ–΄κ°€λ©°

이번 κΈ€μ—μ„œλŠ” μΏ λ²„λ„€ν‹°μŠ€μ˜ λ³΄μ•ˆ 3μš”μ†Œλ₯Ό μ •λ¦¬ν•œλ‹€. RBAC(λˆ„κ°€ 무엇을 ν•  수 μžˆλŠ”κ°€), ServiceAccount(νŒŒλ“œμ˜ 신원), NetworkPolicy(νŒŒλ“œ κ°„ 톡신 ν†΅μ œ)λ₯Ό 톡해 ν΄λŸ¬μŠ€ν„°μ™€ μ• ν”Œλ¦¬μΌ€μ΄μ…˜μ„ λ³΄ν˜Έν•œλ‹€.

λ³΄μ•ˆμ˜ 두 μΆ• β€” RBACλŠ” β€œλˆ„κ°€ μ–΄λ–€ λ¦¬μ†ŒμŠ€μ— 무슨 μž‘μ—…μ„ ν•  수 μžˆλŠ”κ°€β€(μ ‘κ·Ό μ œμ–΄)λ₯Ό, NetworkPolicyλŠ” β€œμ–΄λ–€ νŒŒλ“œκ°€ μ–΄λ–€ νŒŒλ“œμ™€ 톡신할 수 μžˆλŠ”κ°€β€(λ„€νŠΈμ›Œν¬ μ œμ–΄)λ₯Ό λ‹΄λ‹Ήν•œλ‹€. λ‘˜μ€ μ„œλ‘œ λ‹€λ₯Έ 계측을 지킨닀.


1. RBAC β€” Role & Binding

RBAC(Role-Based Access Control)λŠ” μ—­ν• (Role/ClusterRole)을 μ •μ˜ν•˜κ³  바인딩(RoleBinding/ClusterRoleBinding)으둜 μ‚¬μš©μžμ—κ²Œ λΆ€μ—¬ν•œλ‹€.

flowchart LR
    Role["πŸ“œ Role<br/>(κΆŒν•œ μ •μ˜)"]
    Binding["πŸ”— RoleBinding"]
    User["πŸ‘€ User / SA"]
    Role --> Binding --> User
μ˜€λΈŒμ νŠΈλ²”μœ„
Role / RoleBindingνŠΉμ • λ„€μž„μŠ€νŽ˜μ΄μŠ€
ClusterRole / ClusterRoleBindingν΄λŸ¬μŠ€ν„° 전체

Role & RoleBinding (λ„€μž„μŠ€νŽ˜μ΄μŠ€ λ²”μœ„)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# Role β€” dev-nsμ—μ„œ νŒŒλ“œ 쑰회 κΆŒν•œ
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  namespace: dev-ns
  name: pod-reader
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["get", "list", "watch"]
---
# RoleBinding β€” dev-userμ—κ²Œ λΆ€μ—¬
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: read-pods
  namespace: dev-ns
subjects:
- kind: User
  name: "dev-user"
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: Role
  name: pod-reader
  apiGroup: rbac.authorization.k8s.io

ClusterRole & ClusterRoleBinding (ν΄λŸ¬μŠ€ν„° λ²”μœ„)

1
2
3
4
5
6
7
8
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: cluster-admin-role
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["get", "list", "watch", "delete"]

πŸ’‘ Role은 β€œκΆŒν•œμ˜ μ •μ˜β€, Binding은 β€œκΆŒν•œμ˜ λΆ€μ—¬β€λ‘œ λΆ„λ¦¬λ˜μ–΄ μžˆλ‹€. 이 뢄리 덕뢄에 ν•˜λ‚˜μ˜ Role을 μ—¬λŸ¬ μ‚¬μš©μžμ—κ²Œ μž¬μ‚¬μš©ν•  수 μžˆλ‹€. verbs(get/list/delete λ“±)와 resources(pods λ“±)의 μ‘°ν•©μœΌλ‘œ μ„Έλ°€ν•˜κ²Œ κΆŒν•œμ„ μ •ν•œλ‹€.


2. ServiceAccount β€” νŒŒλ“œμ˜ 신원

ServiceAccount(SA)λŠ” νŒŒλ“œκ°€ API μ„œλ²„μ™€ μƒν˜Έμž‘μš©ν•  λ•Œ μ“°λŠ” 계정이닀. μ‚¬λžŒμ΄ μ•„λ‹ˆλΌ μ• ν”Œλ¦¬μΌ€μ΄μ…˜(νŒŒλ“œ)의 신원이닀.

1
kubectl create serviceaccount dev-sa -n dev-ns
1
2
3
4
5
6
7
8
9
10
11
12
apiVersion: v1
kind: Pod
metadata:
  name: sa-pod
  namespace: dev-ns
spec:
  serviceAccountName: dev-sa      # 이 SA의 κΆŒν•œμœΌλ‘œ API μ ‘κ·Ό
  containers:
  - name: nginx
    image: nginx
    ports:
    - containerPort: 80

πŸ’‘ UserλŠ” μ‚¬λžŒ, ServiceAccountλŠ” νŒŒλ“œ(μ•±)의 계정이닀. νŒŒλ“œκ°€ API μ„œλ²„μ— μš”μ²­ν•  λ•Œ SA의 κΆŒν•œμ„ λ”°λ₯΄λ―€λ‘œ, SA에 RBACλ₯Ό 바인딩해 νŒŒλ“œκ°€ ν•  수 μžˆλŠ” 일을 μ œν•œν•œλ‹€.


3. NetworkPolicy β€” νŒŒλ“œ 톡신 ν†΅μ œ

NetworkPolicyλŠ” νŒŒλ“œ κ°„Β·μ™ΈλΆ€μ™€μ˜ νŠΈλž˜ν”½μ„ μ œμ–΄ν•œλ‹€.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
# λͺ¨λ“  νŠΈλž˜ν”½ 차단 (myapp νŒŒλ“œ)
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: deny-all-traffic
  namespace: default
spec:
  podSelector:
    matchLabels:
      app: myapp
  policyTypes:
  - Ingress
  - Egress
  ingress: []
  egress: []
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
# νŠΉμ • λŒ€μ—­Β·ν¬νŠΈλ§Œ ν—ˆμš©
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-specific-traffic
  namespace: default
spec:
  podSelector:
    matchLabels:
      app: myapp
  policyTypes:
  - Ingress
  ingress:
  - from:
    - ipBlock:
        cidr: 192.168.1.0/24
    ports:
    - protocol: TCP
      port: 80

⚠️ NetworkPolicyλŠ” CNIκ°€ 지원해야 λ™μž‘ν•œλ‹€. Calico 같은 μ •μ±… 지원 CNIκ°€ μ—†μœΌλ©΄ 정책을 λ§Œλ“€μ–΄λ„ λ¬΄μ‹œλœλ‹€. 또 기본값은 β€œλͺ¨λ‘ ν—ˆμš©β€μ΄λΌ, ν•œ λ²ˆμ΄λΌλ„ 정책이 뢙은 νŒŒλ“œλŠ” λͺ…μ‹œμ μœΌλ‘œ ν—ˆμš©ν•œ νŠΈλž˜ν”½λ§Œ ν†΅κ³Όμ‹œν‚€λŠ” ν™”μ΄νŠΈλ¦¬μŠ€νŠΈ 방식이 λœλ‹€.


4. Dashboard λ³΄μ•ˆ ꡬ성 μ˜ˆμ‹œ

Dashboard에 κ΄€λ¦¬μž κΆŒν•œμ„ μ£Όλ €λ©΄ SAλ₯Ό λ§Œλ“€κ³  cluster-admin을 λ°”μΈλ”©ν•œλ‹€.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin-user
  namespace: kubernetes-dashboard
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: admin-user
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: admin-user
  namespace: kubernetes-dashboard

⚠️ cluster-admin은 λͺ¨λ“  κΆŒν•œμ„ κ°€μ§„ μ΅œκ°• 역할이닀. νŽΈμ˜μƒ Dashboard μ‹€μŠ΅μ— μ“°μ§€λ§Œ, μ‹€λ¬΄μ—μ„œλŠ” ν•„μš”ν•œ κΆŒν•œλ§Œ 담은 μ»€μŠ€ν…€ ClusterRole을 λ§Œλ“€μ–΄ μ΅œμ†Œ κΆŒν•œ 원칙을 μ§€μΌœμ•Ό ν•œλ‹€.


πŸ“ 정리

1
2
3
4
5
μΏ λ²„λ„€ν‹°μŠ€ λ³΄μ•ˆ
β”œβ”€ RBAC          Role(μ •μ˜) + Binding(λΆ€μ—¬), NS/ν΄λŸ¬μŠ€ν„° λ²”μœ„
β”œβ”€ ServiceAccount νŒŒλ“œμ˜ 신원(μ•±μ˜ API μ ‘κ·Ό κΆŒν•œ)
β”œβ”€ NetworkPolicy  νŒŒλ“œ κ°„ 톡신 ν™”μ΄νŠΈλ¦¬μŠ€νŠΈ(CNI ν•„μš”)
└─ 원칙          μ΅œμ†Œ κΆŒν•œ(cluster-admin λ‚¨μš© X)
κ°œλ…ν•œ 쀄 μ •μ˜
RBACλˆ„κ°€Β·λ¬΄μ—‡μ„Β·ν•  수 μžˆλŠ”κ°€
ServiceAccountνŒŒλ“œ(μ•±)의 계정
NetworkPolicyνŒŒλ“œ 톡신 λ°©ν™”λ²½

μΏ λ²„λ„€ν‹°μŠ€ λ³΄μ•ˆμ˜ 핡심은 RBAC둜 접근을, NetworkPolicy둜 톡신을 ν†΅μ œν•˜λŠ” 것이닀. νŒŒλ“œμ—λŠ” ServiceAccount둜 신원을 λΆ€μ—¬ν•˜κ³ , λͺ¨λ“  κΆŒν•œμ€ μ΅œμ†Œ κΆŒν•œ μ›μΉ™μœΌλ‘œ 쒁게 μ£ΌλŠ” 것이 μ•ˆμ „ν•˜λ‹€.

This post is licensed under CC BY 4.0 by the author.

Comments powered by Disqus.