Access to a privileged container allows for breakout to the underlying host

1. I have seen many ocp containers have set the ""privileged": true" ``` "terminationMessagePolicy": "FallbackToLogsOnError", "imagePullPolicy": "IfNotPresent", "securityContext": { "privileged": true } ``` 2. I just wonder why should the etcd containerd should set the "privileged": true flag. compared to the kubeadm installation, the etcd container has not this flag 3. when using standard container runtimes (for example ContainerD or CRI-O) access to a privileged container allows for easy breakout to the underlying host, which in turn allows for access to all other workloads on that host and credentials for the node agent (Kubelet)