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
I'm just starting with openshift and have decided to try and online version. The first thing I've decided to check is if it's possible to use the free tier as an external runner for my self-hosted gitlab instance. Just mechanically repeated all your nicely written steps but got this in the end:
I suspect that the reason is that these commands did not run properly:
(got Error from server (Forbidden): User "ABC" cannot get securitycontextconstraints at the cluster scope from OC)
Do you know if your template can be theoretically deployed to OpenShift online? Just curious what you think. I also believe that others like may stumble across your repo like me, so this issue can help them too.
The text was updated successfully, but these errors were encountered:
theoretically sa-gitlab-runner service account can be run with builder/deployer permissions (that can be set in OpenShift Online) , though I really don't understand why it tries to create /var/lib/docker/volumes , i.e. gitlab runner there should just connect to kubernetes api and remotely manage tests.
Hi Oleksii and thanks for sharing your template!
I'm just starting with openshift and have decided to try and online version. The first thing I've decided to check is if it's possible to use the free tier as an external runner for my self-hosted gitlab instance. Just mechanically repeated all your nicely written steps but got this in the end:
I suspect that the reason is that these commands did not run properly:
(got
Error from server (Forbidden): User "ABC" cannot get securitycontextconstraints at the cluster scope
from OC)Do you know if your template can be theoretically deployed to OpenShift online? Just curious what you think. I also believe that others like may stumble across your repo like me, so this issue can help them too.
The text was updated successfully, but these errors were encountered: