Changes to origin and OCP images in 3.10

https://github.com/openshift/origin/pull/19509 has been merged and does two things: First, and most important, it puts our images and binaries on a diet: 1. oc is now 110M instead of 220M 2. most origin images were 1.26GB uncompressed (300 or so on the wire) are now half that size (150 on the

CentOS PaaS SIG meeting (2018-05-02)

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 02 May 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- automation - Training for new committee members / Feedback - Open Floor

Re: Using RMI Protocol to connect to OpenShift from external application

Currently, our application is already running on Docker through RMI over SSL. Therefore, we are able to connect our client to the server via SSL and RMI using Docker. What do we have to do in order to make it work with OpenShift, now? 2018-05-02 16:34 GMT+02:00 Joel Pearson

Re: Using RMI Protocol to connect to OpenShift from external application

Selectors refer to labels, so it’d be deploymentconfig.metadata.labels.name SSL/TLS means the client has to support it too. So if there is some option to run RMI over SSL/TLS then it could work pretty easily. But if it’s not possible to run server and client that way then yes, nodeports will be

Re: Using RMI Protocol to connect to OpenShift from external application

Thank you for the response. How can I set up SSL/TLS as a connection method on OpenShift that my Client connects through SSL/TLS to the server? Is that done on the OpenShift router or where can I do the settings? Otherwise, I think NodePorts are the easier solution to establish a connection

Re: Using RMI Protocol to connect to OpenShift from external application

If you're using SSL/TLS you could traverse the Router by use Passthrough. Otherwise, you have to use NodePorts on a Service or something like that. The Router is generally only really for HTTP, but with passthrough SSL/TLS just about anything could be running in the pod. On Wed, May 2, 2018 at

Using RMI Protocol to connect to OpenShift from external application

Hi, we have a application, which is actually running on Wildfly 12.0.0.Final via Docker. Now, we would like to put our application on OpenShift with the existing Dockerfile. However, our client is using RMI to connect connect to the server. Is it still possible to run our application on

Re: Deleteing from WebUI is not working - 3.7.2

Check your controller logs to see if the garbage collector is getting rejected while trying to cleanup the associated resources. You may have to increase the logging level. On Wed, May 2, 2018 at 8:27 AM, Jessica Forrester wrote: > Yeah this typically means the garbage

Re: Deleteing from WebUI is not working - 3.7.2

Yeah this typically means the garbage collector is not able to update the resources to remove its finalizers. You should be seeing errors in the master logs about it. I think there have been a number of root causes for this in the past. Adding David to CC, he is most familiar with the garbage

Re: Deleteing from WebUI is not working - 3.7.2

In addition I've noticed that delete object are using: finalizers. And I believed that this is main issue. The deletionTimestamp is wrong. But I don't know why it is using wrong date and time. Finalizers

Re: Deleteing from WebUI is not working - 3.7.2

When I delete timestamp and entry regarding foreground deletetion (marked on red square): The deleted objects are disappearing right away. 2018-05-02 11:13 GMT+02:00 Łukasz Strzelec : > In addition I've noticed that delete object are using: finalizers. And I >

Re: Deleteing from WebUI is not working - 3.7.2

Hi Jessica:) What I've observed is that each object, that I want to be deleted from UI, has got timestamp with 2h earlier than current time. Looks like some proccess is puting wrong hour into datestamp. I also notice that time on master container is diffrent then on atomic host from where it is