Removed "openshift start node" from origin master

As part of the continuation of splitting OpenShift up to make it be able to run on top of kubernetes, we just merged https://github.com/openshift/origin/pull/20344 which removes "openshift start node" and the "openshift start" commands. This means that the openshift binary will no longer include

How to avoid upgrading to 3.10?

I use ansible to deploy OpenShift. All of my current deployments are 3.9 and I'd like to stay on 3.9 until we can do enough testing on 3.10 to be comfortable upgrading. Can someone point me to any documentation on how to avoid the forced upgrade to 3.10 when I deploy a new instance of OpenShift?

Re: Removed "openshift start node" from origin master

That’s the long term direction, now that many extension points are maturing enough to be useful. But I’ll caution and say the primary goal is to reduce maintenance costs, improve upgrade isolation, and maintain the appropriate level of security, so some of the more nuanced splits might take much

Re: Modify webconsole configmap

Thanks Sam and David. On 08/14/2018 02:44 PM, Sam Padgett wrote: On Mon, Aug 13, 2018 at 10:21 AM Ahmed Ossama > wrote: The documentation https://docs.okd.io/3.10/install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets needs

Re: Modify webconsole configmap

It's a practice resource for `oc cluster up`. Given the target of `oc cluster up`, I don't think we need to update the documentation for it. I can't speak for how the webconsole likes to configure itself. I'd ask Sam. On Mon, Aug 13, 2018 at 3:08 PM Ahmed Ossama wrote: > Thanks David. It

Re: Modify webconsole configmap

On Mon, Aug 13, 2018 at 10:21 AM Ahmed Ossama wrote: > The documentation > https://docs.okd.io/3.10/install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets > needs to be updated to reflect this change. > Hi, Ahmed. The customization doc assumes you are using an