Re: Pulling image from Google Cloud Registry failing with 403

It's not so much that it isn't working, I can't even find a command to remove secrets from service accounts. So what I'm looking for is the 'undo' version of say oc secrets add serviceaccount/builder secrets/google-cloud-registry On 2016-09-15 04:07, Clayton Coleman wrote: Certain secrets

Re: Pulling image from Google Cloud Registry failing with 403

there's no helper command yet. 1.3 will have `oc secrets unlink serviceaccount-name secret-name` On Thu, Sep 15, 2016 at 9:58 AM, Andre Esser wrote: > It's not so much that it isn't working, I can't even find a command to > remove secrets from service accounts. So

Re: Trouble following the Getting Started guide

Thanks for that info. Your suggestion for #2 worked perfectly, I'll open a bug as you suggest. As for #3, it turns out it's all down to being behind a web proxy. I was only setting the upper case versions of the HTTP_PROXY, HTTPS_PROXY and NO_PROXY env vars, which curl was not picking up. The

Trouble following the Getting Started guide

Hi, I've just started looking at OpenShift Origin. I'm attempting to get it going on a CentOS Atomic Host box, and I've been following the Getting Started guide at https://docs.openshift.org/latest/getting_started/ administrators.html#getting-started-administrators, using the method to run origin

Re: Trouble following the Getting Started guide

The first problem is probably because the request hadn't completely finished to import the image. We should report a better error / wait for the import to happen. Please open a bug describing what you did and we'll try to give you a better experience. For #2 - clean up what you did before, and

Re: Trouble following the Getting Started guide

*Generally*, a proxy shouldn't be between the router or master servers and the pods themselves. So in production I would expect you to not have that issue because you should be able to identify your masters via hostname or long term IP (and thus be able to put them in NO_PROXY). Running in a

Re: Origin v1.3.0 released

And of course I almost forget - the *fastest* way to get v1.3.0 is: $ oc cluster up --version=v1.3.0 Enjoy! On Fri, Sep 16, 2016 at 12:51 AM, Clayton Coleman wrote: > Images have been pushed to the hub and release binaries are up on GitHub > under release v1.3.0 >

Origin v1.3.0 released

Images have been pushed to the hub and release binaries are up on GitHub under release v1.3.0 . RPMs will take a few days to show up in the existing channels. v1.3.0 was a huge release - thanks to everyone who contributed to make it

Re: problem with websockets

I don't think that the websocket requests are even hitting the tomcat application. The access logs show hitting the main page, but nothing against the websocket itself. It's like it's not getting past the router. On Thu, Sep 15, 2016 at 4:56 PM, Tony Saxon wrote: > I'll

Re: problem with websockets

Ben, Ram, any ideas? We test web sockets frequently so I assume there's something slightly different about how this app works in docker vs being behind the router. Maybe the headers we send getting misinterpreted via Tomcat? Tony, any errors showing up in tomcat logs (or can you turn on verbose

Re: openshift api swagger 2.0

Cool, thanks! On Thu., 15 Sep. 2016, 12:13 pm Clayton Coleman, wrote: > Coming very soon - 1.4 Kube should have /swagger.json on the root path. > > > On Sep 14, 2016, at 9:44 PM, Andrew Lau wrote: > > > > Hi, > > > > Does anyone know if there is a