Which Kubernetes setting helps prevent cluster-wide escalation from a single namespace role?

Problem Statement

Explanation

Prefer namespace-scoped permissions. ClusterRoleBinding grants rights across the cluster and can turn a small issue into full control.

Code Solution

SolutionRead Only

kubectl create role viewer --verb=get,list,watch --resource=pods -n dev
kubectl create rolebinding viewer-bind --role=viewer --serviceaccount=dev:app -n dev

Practice Sets

This question appears in the following practice sets:

Cloud & Containers

Next Question

Master Interviews
Anywhere, Anytime

Which Kubernetes setting helps prevent cluster-wide escalation from a single namespace role?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Why is a written scope and Rules of Engagement mandatory before any ethical hacking test?

Which ordering matches the common PTES workflow?

In ethical hacking, what does “without authorization” generally imply for legality?

What is the purpose of a Safe Harbor clause in a vulnerability disclosure or bounty program?

Which activity is typically out of scope for standard penetration tests unless explicitly allowed?

More from Ethical hacking

Master Interviews Anywhere, Anytime

Which Kubernetes setting helps prevent cluster-wide escalation from a single namespace role?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Why is a written scope and Rules of Engagement mandatory before any ethical hacking test?

Which ordering matches the common PTES workflow?

In ethical hacking, what does “without authorization” generally imply for legality?

What is the purpose of a Safe Harbor clause in a vulnerability disclosure or bounty program?

Which activity is typically out of scope for standard penetration tests unless explicitly allowed?

More from Ethical hacking

Master Interviews
Anywhere, Anytime