You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug: A clear and concise description of what the bug is.
Good day,
I am facing this issue in OpenShift Kubernetes cluster.
Deployment deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX which is spawned after RWX PVC is created cannot run because of this error:
message: 'pods "nfs-pvc-6011f1fc-49e6-4c0b-a6a7-b2d2f6208e81-5fc49cd65c-" is forbidden:
unable to validate against any security context constraint: [provider "anyuid":
Forbidden: not usable by user or serviceaccount, provider restricted-v2: .containers[0].privileged:
Invalid value: true: Privileged containers are not allowed, provider "restricted":
Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden:
not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable
by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable
by user or serviceaccount, provider "machine-api-termination-handler": Forbidden:
not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden:
not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not
usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable
by user or serviceaccount, provider "node-exporter": Forbidden: not usable by
user or serviceaccount, provider "privileged": Forbidden: not usable by user
or serviceaccount]'
Expected behaviour: A concise description of what you expected to happen
Deployment will run even on OpenShift Kubernetes cluster
Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people gain an understanding of the problem
OpenShift does require service account to be added into privileged scc to be able do some privileged operations. So, I installed OpenEBS with default helm chart way and also had to run these commands.
When I create RWX PVC request, deployment for PVC is spawned with name deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX. This deployment does fail, because it is not running under any service account.
I am able to overcome this issue by editing this deployment and adding there:
Those entries are from pod/openebs-nfs-provisioner-6f579d65cd-cnvgl. But are not present in mentioned deployment.
I understand that this is OpenShift specific issue, still would be fine to have all this working also there.
So my question is - is there currently some way how to tell OpenEBS to spawn deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX with service account ? Maybe I missed some helm chart option or so.
If not, is it possible to add it, please?
Thank you very much
Environment details:
OpenEBS version (use kubectl get po -n openebs --show-labels):
Describe the bug: A clear and concise description of what the bug is.
Good day,
I am facing this issue in OpenShift Kubernetes cluster.
Deployment
deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX
which is spawned after RWX PVC is created cannot run because of this error:Expected behaviour: A concise description of what you expected to happen
Deployment will run even on OpenShift Kubernetes cluster
Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people gain an understanding of the problem
OpenShift does require service account to be added into privileged scc to be able do some privileged operations. So, I installed OpenEBS with default helm chart way and also had to run these commands.
All is running and working fine for RWO volumes.
When I create RWX PVC request, deployment for PVC is spawned with name
deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX
. This deployment does fail, because it is not running under any service account.I am able to overcome this issue by editing this deployment and adding there:
Those entries are from
pod/openebs-nfs-provisioner-6f579d65cd-cnvgl
. But are not present in mentioned deployment.I understand that this is OpenShift specific issue, still would be fine to have all this working also there.
So my question is - is there currently some way how to tell OpenEBS to spawn
deployment.apps/nfs-pvc-XXXXXXXXXXXXXXXXXXXX
with service account ? Maybe I missed some helm chart option or so.If not, is it possible to add it, please?
Thank you very much
Environment details:
kubectl get po -n openebs --show-labels
):kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: