RE: users Digest, Vol 70, Issue 8

Fresh installs. My pods; not the openshift pods. How do I change the scheduling from false to true for masters as that may solve my problem? -Original Message- From: Walters, Todd [mailto:todd_walt...@unigroup.com] Sent: Friday, May 04, 2018 10:54 AM To:

Re: users Digest, Vol 70, Issue 8

Hi Larry, Is it all pods or just the openshift-web-console pods? I’m guessing because, when I upgraded from 3.7 to 3.9 I did not realize that the WebUI was now broke out into it’s own project and running 1 pod per master. I had to change scheduling false to true for my master nodes to allow

Re: Changing ROUTING_SUFFIX?

Yes, that's correct. You will need to update old routes. The rational is that it is a default value not something that is enforced. Regards, Frédéric On Fri, May 4, 2018 at 6:55 PM, Dave Neary wrote: > Thanks - that answers my question. It will work on new routes, but not >

Re: Changing ROUTING_SUFFIX?

Thanks - that answers my question. It will work on new routes, but not old routes - correct? Thanks, Dave. On 05/04/2018 12:52 PM, Frederic Giloux wrote: > Hi Dave, > > the variable was renamed with 3.2: >

Re: Changing ROUTING_SUFFIX?

Hi Dave, the variable was renamed with 3.2: https://docs.openshift.com/enterprise/3.2/install_config/revhistory_install_config.html#thu-may-12-2016 after running ansible you can check /etc/origin/master/master-config.yaml you should have these lines with your value: routingConfig: subdomain:

Re: getting pods running on 3.9 masters

Do you have nodes with the role of COMPUTE? On Fri, May 4, 2018, 5:58 PM Brigman, Larry wrote: > I can get Openshift 3.9 running with anything that openshift-ansible > installs. > When I go to run my pods, I always get Pending on the deployment container. > I've

Re: Changing ROUTING_SUFFIX?

Thanks Frederic, I did this, but the routing suffix still gives the old answer for existing projects - is this expected, or did I do something wrong? Also: I think that in openshift-ansible that the config file is set in roles/openshift_facts/defaults/main.yml as 'osm_default_subdomain' - is

getting pods running on 3.9 masters

I can get Openshift 3.9 running with anything that openshift-ansible installs. When I go to run my pods, I always get Pending on the deployment container. I've tried it with master nodes and with infra nodes in my cluster. Scheduling Failed 0/3 nodes available The nodes all report ready. What is

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

Hi Tien, You just need to create a passthrough route like this: https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#passthrough-termination For it to work, your swing client needs to use SNI (server name identification), so that the OpenShift router knows what

Version settings for installing 3.9

What are the magical set of properties needed to run an ansible install of Origin 3.9 on centos nodes? I've tried various combinations around these but can't get anything to work: openshift_deployment_type=origin openshift_release=v3.9 openshift_image_tag=v3.9.0 openshift_pkg_version=-3.9.0