Lab 5.4 - how to solve the challenge step?
To recap - the challenge is to use what you have learned about service accounts and RBAC roles to limit a psp to the dev-ns namespace.
My idea to solve the challenge is:
1. Create a PSP to allow everything and let everyone use it across all the namespaces.
2. A second PSP (the target) will be only allowed by all the accounts in the dev-ns
namespace.
Phase 1
[email protected]:~$ k get psp privileged Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ NAME PRIV CAPS SELINUX RUNASUSER FSGROUP SUPGROUP READONLYROOTFS VOLUMES privileged true * RunAsAny RunAsAny RunAsAny RunAsAny false * [email protected]:~$ k describe clusterrole psp:privileged Name: psp:privileged Labels: <none> Annotations: <none> PolicyRule: Resources Non-Resource URLs Resource Names Verbs --------- ----------------- -------------- ----- podsecuritypolicies.policy [] [privileged] [use] [email protected]:~$ k describe clusterrolebinding any:psp:privileged Name: any:psp:privileged Labels: <none> Annotations: <none> Role: Kind: ClusterRole Name: psp:privileged Subjects: Kind Name Namespace ---- ---- --------- Group system:serviceaccounts Group system:authenticated [email protected]:~$ k auth can-i --as system:serviceaccounts:dev-ns:simple-sa use psp/privileged Warning: resource 'podsecuritypolicies' is not namespace scoped in group 'policy' yes [email protected]:~$ k auth can-i --as system:serviceaccounts:default:default use psp/privileged Warning: resource 'podsecuritypolicies' is not namespace scoped in group 'policy' yes [email protected]:~$ k auth can-i use psp/privileged Warning: resource 'podsecuritypolicies' is not namespace scoped in group 'policy' yes [email protected]:~$
Phase 2
[email protected]:~/5$ k -n dev-ns get psp Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ NAME PRIV CAPS SELINUX RUNASUSER FSGROUP SUPGROUP READONLYROOTFS VOLUMES no-priv false RunAsAny MustRunAsNonRoot RunAsAny RunAsAny false * privileged true * RunAsAny RunAsAny RunAsAny RunAsAny false * [email protected]:~/5$ k -n dev-ns describe role psp:no-priv Name: psp:no-priv Labels: <none> Annotations: <none> PolicyRule: Resources Non-Resource URLs Resource Names Verbs --------- ----------------- -------------- ----- podsecuritypolicies.policy [] [no-priv] [use] [email protected]:~/5$ k -n dev-ns describe rolebinding any:psp:no-priv Name: any:psp:no-priv Labels: <none> Annotations: <none> Role: Kind: Role Name: psp:no-priv Subjects: Kind Name Namespace ---- ---- --------- Group system:authenticated Group system:serviceaccounts:dev-ns [email protected]:~/5$ k -n dev-ns auth can-i --as system:serviceaccount:dev-ns:default use psp/no-priv Warning: resource 'podsecuritypolicies' is not namespace scoped in group 'policy' yes [email protected]:~/5$ k -n dev-ns auth can-i use psp/no-priv Warning: resource 'podsecuritypolicies' is not namespace scoped in group 'policy' yes [email protected]:~/5$ k -n dev-ns get pod,rs,deploy No resources found in dev-ns namespace. [email protected]:~/5$
Now I am going to create the pod db-one
and deployment db-two
in the dev-ns
namespace. The respective pods require to run as root, which is forbidden by the no-priv
policy - we already saw it earlier in the lab. My expectation is that the policy would prevent the pods from starting:
[email protected]:~/5$ k run --image=mariadb db-one --port=3306 --env="[email protected]" -n dev-ns pod/db-one created [email protected]:~/5$ k create -f db-two.yaml deployment.apps/db-two created [email protected]:~/5$ k -n dev-ns get pod,rs,deploy NAME READY STATUS RESTARTS AGE pod/db-one 0/1 ContainerCreating 0 14s pod/db-two-cfb5c47db-llbq8 0/1 ContainerCreating 0 3s NAME DESIRED CURRENT READY AGE replicaset.apps/db-two-cfb5c47db 1 1 0 3s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/db-two 0/1 1 0 3s [email protected]:~/5$
And already we can see that my idea does not work. If the no-priv
policy actually worked in the dev-ns
namespace, then the replica controller would not have been able to create the pod, but it did. And right now the situation is that all is running, despite my expectations:
[email protected]:~/5$ k -n dev-ns get pod,rs,deploy NAME READY STATUS RESTARTS AGE pod/db-one 1/1 Running 0 2m30s pod/db-two-cfb5c47db-llbq8 1/1 Running 0 2m19s NAME DESIRED CURRENT READY AGE replicaset.apps/db-two-cfb5c47db 1 1 1 2m19s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/db-two 1/1 1 1 2m19s [email protected]:~/5$
So my scheme does not work and I have no idea how to solve the challenge. Please, help. Thank you.
Categories
- 9.9K All Categories
- 29 LFX Mentorship
- 82 LFX Mentorship: Linux Kernel
- 463 Linux Foundation Boot Camps
- 266 Cloud Engineer Boot Camp
- 93 Advanced Cloud Engineer Boot Camp
- 43 DevOps Engineer Boot Camp
- 28 Cloud Native Developer Boot Camp
- 1 Express Training Courses
- 1 Express Courses - Discussion Forum
- 1.6K Training Courses
- 17 LFC110 Class Forum
- 3 LFC131 Class Forum
- 19 LFD102 Class Forum
- 130 LFD103 Class Forum
- 9 LFD121 Class Forum
- 59 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 544 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 20 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 35 LFS207 Class Forum
- 295 LFS211 Class Forum
- 53 LFS216 Class Forum
- 45 LFS241 Class Forum
- 39 LFS242 Class Forum
- 33 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 962 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 85 LFS260 Class Forum
- 124 LFS261 Class Forum
- 29 LFS262 Class Forum
- 78 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 16 LFS268 Class Forum
- 14 LFS269 Class Forum
- 193 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 205 LFW211 Class Forum
- 148 LFW212 Class Forum
- 890 Hardware
- 212 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 206 Networking
- 99 Printers & Scanners
- 85 Storage
- 747 Linux Distributions
- 88 Debian
- 64 Fedora
- 13 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 354 Ubuntu
- 468 Linux System Administration
- 38 Cloud Computing
- 67 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 77 Network Management
- 107 System Management
- 48 Web Management
- 61 Mobile Computing
- 22 Android
- 25 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 525 Off Topic
- 127 Introductions
- 211 Small Talk
- 19 Study Material
- 782 Programming and Development
- 256 Kernel Development
- 492 Software Development
- 919 Software
- 255 Applications
- 181 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 46 All In Program
- 46 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)