BuildRequest name parameter

What is the purpose of the {name} URL parameter for the instantiate in BuildRequests? ie. POST /oapi/v1/namespaces/{namespace}/buildconfigs/{name}/instantiate https://docs.openshift.org/latest/rest_api/openshift_v1.html#create-instantiate-of-a-buildrequest The docs seem to suggest it's the name

Re: Using Custom SCC and Service Account in Deployment

Thanks all. What was mentioned by Graham was the issue; I was not in the correct project. On Thu, Jul 27, 2017 at 5:46 AM, Graham Dumpleton wrote: > What is documented in that blog does work. > > Instead of: > > oc adm policy add-scc-to-user anyuid

Re: Using Custom SCC and Service Account in Deployment

What is documented in that blog does work. Instead of: oc adm policy add-scc-to-user anyuid system:serviceaccount:mysvcacct use: oc adm policy add-scc-to-user anyuid -z mysvcacct as the blog explains, and make sure you are in the correct project in case when you switched to admin you

Re: Using Custom SCC and Service Account in Deployment

The uid assigned is not random. It is the first uid of a range assigned to the namespace. The value is stored on the namespace as an annotation. The SCC looks at that range when interpreting MustRunAsRange. You can set the annotation yourself as you see fit On Jul 26, 2017, at 2:50 PM, Isuru

Using Custom SCC and Service Account in Deployment

Hi all, I'm trying to allow Docker containers to be run in openshift using the user specified in the Dockerfile itself, without using a random user id. I see that its possible to do this using the command [1], where all authenticated users will be added to the anyuid group. Without doing this for