DevOps / SRE / Platform Engineer / Stage 9 · Operating a cluster
Bound permissions and scale workloads
"Already know" meets prerequisites. "Not relevant" removes the topic from your total but leaves what builds on it waiting.
Self-check
- Give a team a namespace with a quota and a role that can deploy but not read secrets, prove each limit with a refused request, and make a Deployment scale on CPU.
- Evidence to include: Keep the Role, binding and quota, the refused requests (kubectl auth can-i and a pod over quota), and the autoscaler's events.
Try it without the material first, then compare. Save your answer in your notes below. Report a problem with this self-check
Learning activities
3 activities- Not doneUsing RBAC Authorization (opens another site)
Roles, cluster roles and bindings, and how RBAC prevents privilege escalation.
20 min - Not doneResource Quotas (opens another site)
Capping what a namespace may consume in total.
12 min - Not doneHorizontal Pod Autoscaling (opens another site)
How the autoscaler adds and removes replicas from metrics, and how to stop it flapping.
15 min