Re: Push to registry sometimes fails

Yeah, I secured the registry, however I couldn't get pushing to work when using the tls certificates.. I kept getting "Error: x509: certificate signed by unknown authority" when using the master's ca.crt coppied into /etc/docker/certs.d/172.30.25.196:5000/ca.crt I tried going throgh the secure

Re: Push to registry sometimes fails

Docker assumes that the registry talks TLS. It will only use http if you specify the registry is insecure (typically via '--insecure-registry 172.30.0.0/16' in /etc/sysconfig/docker). Is your registry secured? On Wed, Dec 7, 2016 at 8:11 PM, Cameron Braid wrote: > I am

Push to registry sometimes fails

I am occasional getting this error after a build when pushing to the internal registry : Pushed 10/12 layers, 83% complete Registry server Address: Registry server User Name: serviceaccount Registry server Email: serviceacco...@example.org Registry server Password: <> error: build error: Failed

OpenShift S2I cannot push image on EC2

Folks, there seems to be an authentication problem in OpenShift when installed on EC2. [INFO] [INFO] BUILD SUCCESS [INFO]

Re: OpenShift origin cluster in VLAN

Each master still needs an IP registered that then backs the Kubernetes service that clients use to talk to the API. So verify that each master is reporting the correct IP that is reachable from all nodes to "oc get endpoints kubernetes -n defaults" On Dec 7, 2016, at 9:39 AM, Den Cowboy

Re: OpenShift origin cluster in VLAN

On Wed, Dec 7, 2016 at 9:37 AM, Den Cowboy wrote: > We've installed OpenShift origin with the advanced playbook. There we used > public ip's. But after the installation we've deleted the public ip's. The > master and nodes are in a VLAN. I'm able to create a user,

Re: Jenkins Windows Slave

I suspect the router isn't working with the JNLP connection since it's not an http protocol, you may need to expose your jenkins master via an external ip, or a nodeport, in order to make it possible for slaves to connect to it.

OpenShift origin cluster in VLAN

We've installed OpenShift origin with the advanced playbook. There we used public ip's. But after the installation we've deleted the public ip's. The master and nodes are in a VLAN. I'm able to create a user, authenticate, visite the webconsole. restart node, master configs. I'm able to pull

Jenkins Windows Slave

Hi Is it possible to add an existing windows machine as a slave to a Jenkins master running on Openshift? I exposed the jnlp service with a route in Openshift and tried to use the tunnel option with 1) a Java Web Start slave, 2) running the slave client jar directly and 3) a Swarm slave. None of

Re: Liveness probe frequency

Hi Krzysztof there is the option "--period-seconds" with "oc set probe", confer: "oc set probe --help". Regards, Frédéric On Wed, Dec 7, 2016 at 11:12 AM, Sobkowiak Krzysztof < krzys.sobkow...@gmail.com> wrote: > Hi > > Is it possible to set the frequency the liveness/readiness probes are >

Re: Liveness probe frequency

Try this: oc explain pod.spec.containers.livenessProbe Look for initialDelaySeconds and periodSeconds. M. On 07. 12. 2016 11:12, Sobkowiak Krzysztof wrote: Hi Is it possible to set the frequency the liveness/readiness probes are performed? If yes, how can I do it in OpenShift? Kindly

Re: Liveness probe frequency

Hi. Yes, you can set periodSeconds of the probe. More info in the docs at https://docs.openshift.org/latest/rest_api/openshift_v1.html#v1-probe -- Mateus Caruccio / Master of Puppets GetupCloud.com - Eliminamos a Gravidade On Wed, Dec 7, 2016 at 8:12 AM, Sobkowiak Krzysztof <

Liveness probe frequency

Hi Is it possible to set the frequency the liveness/readiness probes are performed? If yes, how can I do it in OpenShift? Kindly regards Krzysztof -- Krzysztof Sobkowiak JEE & OSS Architect, Integration Architect Apache Software Foundation Member (http://apache.org/) Apache ServiceMix