Re: Re-configure openshift cluster using ansible

Thanks. But when I need to change things that a bit more like different hostnames or certificates, what should I run? Upgrade? > On 22 Nov 2017, at 2:32, Joel Pearson wrote: > > For reference what you're after is: > > openshift_disable_check=disk_availability >

Re: Re-configure openshift cluster using ansible

For reference what you're after is: openshift_disable_check=disk_availability On Wed, Nov 22, 2017 at 5:05 AM Scott Dodson wrote: > It really depends on the configuration changes you want to make whether or > not you can simply re-run config.yml and get what you're looking

Re: OpenShift registry behind registry auth issues

After some internal discussion we've decided that we'll fix this by adding the service ip address to the default NO_PROXY list. Follow the bug for any further updates. On Tue, Nov 21, 2017 at 10:29 AM, Scott Dodson wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1511870

Re: Re-configure openshift cluster using ansible

It really depends on the configuration changes you want to make whether or not you can simply re-run config.yml and get what you're looking for. Things like hostnames that get placed in certs and certain network configuration such as services and cluster CIDR ranges are immutable and cannot be

Re-configure openshift cluster using ansible

Hello, I could not figure out how I can change the inventory file for new configurations and then Re-configure my current cluster. Whenever I re run the configure.yml in the byo folder, it checks again the minimal requirements and my /var is already less than 40G after the installation.

Re: OpenShift registry behind registry auth issues

https://bugzilla.redhat.com/show_bug.cgi?id=1511870 is the bug, we haven't fixed it yet. We're debating whether or not to switch to using the dns name, though if environment variables evaluate as expected perhaps we should just add NO_PROXY=${KUBENETES_SERVICE_HOST} and then we can address whether

Re: OpenShift registry behind registry auth issues

On Tue, Nov 21, 2017 at 1:46 AM, Joel Pearson wrote: > Hi, > > I spend most of the day debugging why my OpenShift registry wasn’t working > because the cluster lives behind a http proxy. I can see OpenShift ansible > configured the registry with proxy settings

GlusterFS Autoprovisioning with Heketi - Permission Problem/Question

Hello, we are new to OpenShift and are "playing" with it in our lab. We have setup Openshift Origin 3.6 with a dedicated 3 node Glusterfs storage (CentOS based) with distributed/replicated. Due to the excellent documentation we have achieved to setup autoprovisioning according to this guide