how to control access for pods/exec only in kubernetes rbac without pods create binded?

Question

I checked the kubernetes docs, find that pods/exec resources has no verb, and do not know how to only control access for it? Since I create a pod, someone else need to access it use 'exec' but cannot create anything in my cluster.

How to implement this?

score 60 · Answer 1 · edited Jan 03 '20 at 13:31

60

Since pods/exec is a subresource of pods, If you want to exec a pod, you first need to get the pod, so here is my role definition.

kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  namespace: default
  name: pod-reader
rules:
- apiGroups: [""]
  resources: ["pods", "pods/log"]
  verbs: ["get", "list"]
- apiGroups: [""]
  resources: ["pods/exec"]
  verbs: ["create"]

edited Jan 03 '20 at 13:31

Ivan Aracki

4,861
11
59
73

answered Nov 27 '17 at 02:29

peteyuan

1,214
1
11
11

4

i know a bit late .. but is therre a way to inherit all sub ressources? – Flowkap Oct 11 '19 at 10:57
You mean all namespaces? Replace `Role` with `ClusterRole`. – Max Lobur Nov 05 '19 at 13:50
1

I have been trying to find this pods and pods/exec in the documentation but I couldn't. Could you please state the link of that in the docs? – Mohammed Noureldin Oct 13 '22 at 22:39

score 0 · Answer 2 · edited Mar 25 '22 at 08:43

Maybe you can try this kubectl plugin: https://github.com/zhangweiqaz/go_pod

kubectl go -h
kubectl exec in pod with username. For example:
kubectl go pod_name

Usage:
  go [flags]

Flags:
  -c, --containerName string   containerName
  -h, --help                   help for go
  -n, --namespace string       namespace
  -u, --username string        username, this user must exist in image, default: dev

how to control access for pods/exec only in kubernetes rbac without pods create binded?

2 Answers2

Linked