Extended build support is being removed - use chained builds instead

After much deliberation we've concluded that the chained builds[1] pattern is a better approach for producing runtime-only application images, compared with the experimental extended builds feature. As a result, we will be removing the extended builds feature from the v3.7 release[2]. Advantages

Possible to use AWS elasitcsearch for OpenShift logging?

I have built out a cluster on AWS using the ansible advanced install. I see that i can setup logging by creating infrastructure nodes that will host elasticsearch. AWS has an elasticsearch service. Is there a way to use that instead? Thanks Marc ___

Re: Single node cluster

Hi, for non-critical workloads I find `oc-cluster-wrapper` very convenient. You can wipe and recreate installations quickly when needed. Just make sure you script all post-install configuration like configuring users, etc. I find it more problematic that if you recreate the cluster you would

Re: Origin router and X-Forwarded-For

Title: Re: Origin router and X-Forwarded-For Hi Marcello Lorenzi. have you used -servername in s_client? The ssl solution is based on sni ( https://en.wikipedia.org/wiki/Server_Name_Indication ) Regards Aleks on Donnerstag, 12. Oktober 2017 at 13:02 was written: Hi All, thanks for the

Re: Origin router and X-Forwarded-For

Hi All, thanks for the response and we checked the configuration. If I tried to check the certificated propagate with the passthrough configuration with openssl s_client and the certificate provided is the wilcard domain certificate and not the pod itself. Is it normal? Thanks, Marcello On Thu,

Re: Origin router and X-Forwarded-For

Title: Re: Origin router and X-Forwarded-For Hi. Additionally to joel suggestion can you also use reencrypted route if you want to talk encrypted with apache webserver. https://docs.openshift.org/3.6/architecture/networking/routes.html#re-encryption-termination Regards Aleks on Mittwoch, 11.