As Aaron suggested it can be done using the instructions here https://docs.openshift.org/latest/install_config/web_console_customization.html#serving-static-files the path is relative to where the master config file is.
There was a technical discussion about this when we originally added the links, and the decision was that we did not want that behavior OOTB because of the extra load it would put on the master having users downloading the binary through it, particularly for large deployments. We can revisit that discussion if we need to. On Tue, Jul 19, 2016 at 9:41 AM, Scott Dodson <[email protected]> wrote: > Jessica, > > Can the asset server be configured to expose a directory on the host > for downloads such as /usr/share/openshift/clients ? If we had that > the installer could install the redistributable clients package on > masters and configure those values such that users could download the > clients from the console they're interacting with. > > -- > Scott > > On Tue, Jul 19, 2016 at 9:11 AM, Jessica Forrester <[email protected]> > wrote: > > Those links are fully customizable for that purpose, if you want to host > the > > binaries somewhere else for people using your openshift cluster then you > can > > override the locations. > > > https://docs.openshift.org/latest/install_config/web_console_customization.html#adding-or-changing-links-to-download-the-cli > > > > On Tue, Jul 19, 2016 at 8:58 AM, Dusty Mabe <[email protected]> wrote: > >> > >> > >> > >> On 07/19/2016 01:02 AM, Jonathan Yu wrote: > >> > Hey Dusty, > >> > > >> > Steve was trying to explain that you can: > >> > >> Yep. I understood what he sent and it was very helpful :) > >> > >> > > >> > 1. Log in to the OpenShift Web Console for the instance you are using > >> > 2. Click the "(?)" button on the upper left of the navigation menu > bar, > >> > next to your username, and click "About" in the dropdown menu that > appears > >> > 3. There are links on the page to download the CLI tools > >> > >> Right. The links are there, but they point to the RH customer portal > >> and you have to log in etc, etc.. I was proposing a case where it > >> would be more useful to just host the client binaries directly rather > >> than linking somewhere else. > >> > >> There could be arguments for doing this or not doing this. I'd just > >> like to bring it up as an option. We could even have a link to the > >> "this version of openshift client" as well as link to the customer > >> portal for the "latest version of the openshift client". > >> > >> Thoughts? > >> > >> > >> > 4. It also shows the command you'll need (including an access token) > to > >> > log in to the instance, so it's *extremely* convenient :) > >> > > >> > Then you can follow the instructions here (there's a screenshot): > >> > > https://docs.openshift.com/enterprise/3.2/cli_reference/get_started_cli.html#installing-the-cli > >> > > >> > So if I'm reading your emails correctly, it seems we already have what > >> > you're looking for (at least in OSE 3.2, not sure when it was > introduced). > >> > Hope this helps clarify what Steve has said. > >> > > >> > Would this have been clearer if there was a screenshot of the "?" > button > >> > and dropdown? If so, we can open an issue to have the documentation > updated > >> > accordingly. > >> > > >> > >> > >> > >> _______________________________________________ > >> dev mailing list > >> [email protected] > >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > > > > > _______________________________________________ > > dev mailing list > > [email protected] > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
