<p>I'm creating a pod through the <code>KubernetesPodOperator</code> in Airflow. This pod should mount a Google Cloud Storage to <code>/mnt/bucket</code> using <code>gcsfuse</code>. For this, the pod is required to be started with the <code>securityContext</code> parameter, such that it can become 'privileged'.</p>

<p>It is <a href="https://stackoverflow.com/questions/52742455/airflow-kubernetespodoperator-pass-securitycontext-parameter">currently not possible</a> to pass the securityContext parameter through Airflow. Is there another way to work around this? Perhaps by setting a 'default' securityContext before the pods are even started? I've looked at creating a <code>PodSecurityPolicy</code>, but haven't managed to figure out a way.</p>

bartcode
<p>Separate from the Mutating Admission Controller, it's also possible to deploy a DaemonSet into your cluster that mounts <code>/mnt/bucket</code> onto the host filesystem, and the the Airflow pods would use <code>{"name": "bucket", "hostPath": {"path": "/mnt/bucket"}}</code> as their <code>volume:</code>, which -- assuming it works -- would be a <strong>boatload</strong> less typing, and also not run the very grave risk of a Mutating Admission Controller borking your cluster and causing Pods to be mysteriously mutated</p>
