The current doc was outdated and hardcoded, so removing the example from the doc and add a proper psp.yaml file that people can use and contribute too. Closes: https://github.com/rook/rook/issues/3309 Signed-off-by: Sébastien Han <seb@redhat.com>
3.3 KiB
title, weight, indent
| title | weight | indent |
|---|---|---|
| Ceph cluster Pod Security Policies | 1400 | true |
Using Rook-Ceph with Pod Security Policies (PSPs)
See the Rook overall PSP document before continuing on here with Ceph specifics.
PodSecurityPolicy
You need at least one PodSecurityPolicy that allows privileged Pod execution. Please look at https://github.com/rook/rook/cluster/examples/kubernetes/ceph/psp.yaml for a reasonably pared down for Ceph.
Hint: Allowing hostNetwork usage is required when using hostNetwork: true in the Cluster
Resource Definition! You are then also required to allow the usage of hostPorts in the
PodSecurityPolicy. The given port range is a minimal working recommendation for a Rook Ceph cluster:
hostPorts:
# Ceph msgr2 port
- min: 3300
max: 3300
# Ceph ports
- min: 6789
max: 7300
# Ceph MGR Prometheus Metrics
- min: 9283
max: 9283
ClusterRole and ClusterRoleBinding
Next up you require a ClusterRole and a corresponding ClusterRoleBinding, which enables the Rook Agent ServiceAccount to run the rook-ceph-agent Pods on all nodes
with privileged rights. Here are the definitions:
# privilegedPSP grants access to use the privileged PSP.
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: psp:rook
rules:
- apiGroups:
- policy
resources:
- podsecuritypolicies
resourceNames:
- privileged
verbs:
- use
and
apiVersion: v1
kind: Namespace
metadata:
name: rook-ceph-system
---
# Allow the rook-ceph-system serviceAccount to use the privileged PSP
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: rook-ceph-system-psp
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: psp:rook
subjects:
- kind: ServiceAccount
name: rook-ceph-system
namespace: rook-ceph
Save these definitions to one or multiple yaml files and create them by executing kubectl apply -f <nameOfYourFile>.yaml
You will also require two more RoleBindings for each Rook Cluster you deploy:
Create these two RoleBindings in the Namespace you plan to deploy your Rook Cluster into (default is "rook" namespace):
apiVersion: v1
kind: Namespace
metadata:
name: rook-ceph
---
# Allow the default serviceAccount to use the privileged PSP
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: rook-default-psp
namespace: rook-ceph
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: psp:rook
subjects:
- kind: ServiceAccount
name: default
namespace: rook-ceph
---
# Allow the rook-ceph-osd serviceAccount to use the privileged PSP
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: rook-ceph-osd-psp
namespace: rook-ceph
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: psp:rook
subjects:
- kind: ServiceAccount
name: rook-ceph-osd
namespace: rook-ceph
---
# Allow the rook-ceph-mgr serviceAccount to use the privileged PSP
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: rook-ceph-mgr-psp
namespace: rook-ceph
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: psp:rook
subjects:
- kind: ServiceAccount
name: rook-ceph-mgr
namespace: rook-ceph