Customizing the Web Console

You are viewing documentation for a release that is no longer supported. The latest supported version of version 3 is [3.11]. For the most recent version 4, see [4]

You are viewing documentation for a release that is no longer supported. The latest supported version of version 3 is [3.11]. For the most recent version 4, see [4]

Overview

Administrators can customize the web console using extensions, which let you run scripts and load custom stylesheets when the web console loads. Extension scripts allow you to override the default behavior of the web console and customize it for your needs.

For example, extension scripts can be used to add your own company’s branding or to add company-specific capabilities. A common use case for this is rebranding or white-labeling for different environments. You can use the same extension code, but provide settings that change the web console.

Take caution making extensive changes to the web console styles or behavior that are not documented below. While you add any scripts or stylesheets, significant customizations might need to be reworked on upgrades as the web console markup and behavior change in future versions.

Loading Extension Scripts and Stylesheets

As of OKD 3.9, extension scripts and stylesheets can be hosted at any https:// URL as long as the URL is accessible from the browser. The files might be hosted from a pod on the platform using a publicly accessible route, or on another server outside of OKD.

To add scripts and stylesheets, edit the webconsole-config ConfigMap in the openshift-web-console namespace. The web console configuration is available in the webconsole-config.yaml key of the ConfigMap.

  1. $ oc edit configmap/webconsole-config -n openshift-web-console

To add scripts, update the extensions.scriptURLs property. The value is an array of URLs.

To add stylesheets, update the extensions.stylesheetURLs property. The value is an array of URLs.

Example extensions.stylesheetURLs Setting

  1. apiVersion: v1
  2. kind: ConfigMap
  3. data:
  4.   webconsole-config.yaml: |
  5.     apiVersion: webconsole.config.openshift.io/v1
  6.     extensions:
  7.       scriptURLs:
  8.         - https://example.com/scripts/menu-customization.js
  9.         - https://example.com/scripts/nav-customization.js
  10.       stylesheetURLs:
  11.         - https://example.com/styles/logo.css
  12.         - https://example.com/styles/custom-styles.css
  13.     [...]

After saving the ConfigMap, the web console containers will be updated automatically for the new extension files within a few minutes.

Scripts and stylesheets must be served with the correct content type or they will not be run by the browser. Scripts must be served with Content-Type: application/javascript and stylesheets with Content-Type: text/css.

It is a best practice to wrap extension scripts in an Immediately Invoked Function Expression (IIFE). This ensures that you do not create global variables that conflict with the names used by the web console or by other extensions. For example:

  1. (function() {
  2.   // Put your extension code here...
  3. }());

The examples in the following sections show common ways you can customize the web console.

Additional extension examples are available in the OpenShift Origin repository on GitHub.

Setting Extension Properties

If you have a specific extension, but want to use different text in it for each of the environments, you can define the environment in the web console configuration, and use the same extension script across environments.

To add extension properties, edit the webconsole-config ConfigMap in the openshift-web-console namespace. The web console configuration is available in the webconsole-config.yaml key of the ConfigMap.

  1. $ oc edit configmap/webconsole-config -n openshift-web-console

Update the extensions.properties value, which is a map of key-value pairs.

  1. apiVersion: v1
  2. kind: ConfigMap
  3. data:
  4.   webconsole-config.yaml: |
  5.     apiVersion: webconsole.config.openshift.io/v1
  6.     extensions:
  7.       [...]
  8.       properties:
  9.         doc_url: https://docs.openshift.com
  10.         key1: value1
  11.         key2: value2
  12.     [...]

This results in a global variable that can be accessed by the extension, as if the following code was executed:

  1. window.OPENSHIFT_EXTENSION_PROPERTIES = {
  2.   doc_url: "https://docs.openshift.com",
  3.   key1: "value1",
  4.   key2: "value2"
  5. }

Extension Option for External Logging Solutions

As of OKD 3.6, there is an extension option to link to external logging solutions instead of using OKD’s EFK logging stack:

  1. 'use strict';
  2. angular.module("mylinkextensions", ['openshiftConsole'])
  3.        .run(function(extensionRegistry) {
  4.           extensionRegistry.add('log-links', _.spread(function(resource, options) {
  5.             return {
  6.               type: 'dom',
  7.               node: '<span><a href="https://extension-point.example.com">' + resource.metadata.name + '</a><span class="action-divider">|</span></span>'
  8.             };
  9.           }));
  10.        });
  11. hawtioPluginLoader.addModule("mylinkextensions");

Add the script as described in Loading Extension Scripts and Stylesheets.

Customizing and Disabling the Guided Tour

A guided tour will pop up the first time a user logs in on a particular browser. You can enable the auto_launch for new users:

  1. window.OPENSHIFT_CONSTANTS.GUIDED_TOURS.landing_page_tour.auto_launch = true;

Add the script as described in Loading Extension Scripts and Stylesheets.

Customizing Documentation Links

Documentation links on the landing page are customizable. window.OPENSHIFT_CONSTANTS.CATALOG_HELP_RESOURCES is an array of objects containing a title and an href. These will be turned into links. You can completely override the array, push or pop additional links, or modify the attributes of existing links. For example:

  1. window.OPENSHIFT_CONSTANTS.CATALOG_HELP_RESOURCES.links.push({
  2.   title: 'Blog',
  3.   href: 'https://blog.openshift.com'
  4. });

Add the script as described in Loading Extension Scripts and Stylesheets.

Customizing the Logo

The following style changes the logo in the web console header:

  1. #header-logo {
  2.   background-image: url("https://www.example.com/images/logo.png");
  3.   width: 190px;
  4.   height: 20px;
  5. }

Replace the example.com URL with a URL to an actual image, and adjust the width and height. The ideal height is 20px.

Add the stylesheet as described in Loading Extension Scripts and Stylesheets.

Customizing the Membership Whitelist

The default whitelist in the membership page shows a subset of cluster roles, such as admin, basic-user, edit, and so on. It also shows custom roles defined within a project.

For example, to add your own set of custom cluster roles to the whitelist:

  1. window.OPENSHIFT_CONSTANTS.MEMBERSHIP_WHITELIST = [
  2.   "admin",
  3.   "basic-user",
  4.   "edit",
  5.   "system:deployer",
  6.   "system:image-builder",
  7.   "system:image-puller",
  8.   "system:image-pusher",
  9.   "view",
  10.   "custom-role-1",
  11.   "custom-role-2"
  12. ];

Add the script as described in Loading Extension Scripts and Stylesheets.

Changing Links to Documentation

Links to external documentation are shown in various sections of the web console. The following example changes the URL for two given links to the documentation:

  1. window.OPENSHIFT_CONSTANTS.HELP['get_started_cli']      = "https://example.com/doc1.html";
  2. window.OPENSHIFT_CONSTANTS.HELP['basic_cli_operations'] = "https://example.com/doc2.html";

Alternatively, you can change the base URL for all documentation links.

This example would result in the default help URL https://example.com/docs/welcome/index.html:

  1. window.OPENSHIFT_CONSTANTS.HELP_BASE_URL = "https://example.com/docs/"; (1)
1The path must end in a /.

Add the script as described in Loading Extension Scripts and Stylesheets.

Adding or Changing Links to Download the CLI

The About page in the web console provides download links for the command line interface (CLI) tools. These links can be configured by providing both the link text and URL, so that you can choose to point them directly to file packages, or to an external page that points to the actual packages.

For example, to point directly to packages that can be downloaded, where the link text is the package platform:

  1. window.OPENSHIFT_CONSTANTS.CLI = {
  2.   "Linux (32 bits)": "https://<cdn>/openshift-client-tools-linux-32bit.tar.gz",
  3.   "Linux (64 bits)": "https://<cdn>/openshift-client-tools-linux-64bit.tar.gz",
  4.   "Windows":         "https://<cdn>/openshift-client-tools-windows.zip",
  5.   "Mac OS X":        "https://<cdn>/openshift-client-tools-mac.zip"
  6. };

Alternatively, to point to a page that links the actual download packages, with the Latest Release link text:

  1. window.OPENSHIFT_CONSTANTS.CLI = {
  2.   "Latest Release": "https://<cdn>/openshift-client-tools/latest.html"
  3. };

Add the script as described in Loading Extension Scripts and Stylesheets.

Customizing the About Page

To provide a custom About page for the web console:

  1. Write an extension that looks like:

    1. angular
    2.   .module('aboutPageExtension', ['openshiftConsole'])
    3.   .config(function($routeProvider) {
    4.     $routeProvider
    5.       .when('/about', {
    6.         templateUrl: 'https://example.com/extensions/about/about.html',
    7.         controller: 'AboutController'
    8.       });
    9.     }
    10.   );
    12. hawtioPluginLoader.addModule('aboutPageExtension');

  2. Write a customized template.

    Start from the version of about.html from the OpenShift Container Platform release you are using. Within the template, there are two angular scope variables available: version.master.openshift and version.master.kubernetes.

  3. Host the template at a URL with the correct Cross-Origin Resource Sharing (CORS) response headers for the web console.

    1. Set Access-Control-Allow-Origin response to allow requests from the web console domain.

    2. Set Access-Control-Allow-Methods to include GET.

    3. Set Access-Control-Allow-Headers to include Content-Type.

Alternatively, you can include the template directly in your JavaScript using AngularJS $templateCache.

Add the script as described in Loading Extension Scripts and Stylesheets.

Configuring Navigation Menus

Top Navigation Dropdown Menus

The top navigation bar of the web console contains the help icon and the user dropdown menus. You can add additional menu items to these using the angular-extension-registry.

The available extension points are:

  • nav-help-dropdown - the help icon dropdown menu, visible at desktop screen widths

  • nav-user-dropdown - the user dropdown menu, visible at desktop screen widths

  • nav-dropdown-mobile - the single menu for top navigation items at mobile screen widths

The following example extends the nav-help-dropdown menu, with a name of <myExtensionModule>:

<myExtensionModule> is a placeholder name. Each dropdown menu extension must be unique enough so that it does not clash with any future angular modules.

  1. angular
  2.   .module('<myExtensionModule>', ['openshiftConsole'])
  3.   .run([
  4.     'extensionRegistry',
  5.     function(extensionRegistry) {
  6.       extensionRegistry
  7.         .add('nav-help-dropdown', function() {
  8.           return [
  9.             {
  10.               type: 'dom',
  11.               node: '<li><a href="http://www.example.com/report" target="_blank">Report a Bug</a></li>'
  12.             }, {
  13.               type: 'dom',
  14.               node: '<li class="divider"></li>'  // If you want a horizontal divider to appear in the menu
  15.             }, {
  16.               type: 'dom',
  17.               node: '<li><a href="http://www.example.com/status" target="_blank">System Status</a></li>'
  18.             }
  19.           ];
  20.         });
  21.     }
  22.   ]);
  24. hawtioPluginLoader.addModule('<myExtensionModule>');

Add the script as described in Loading Extension Scripts and Stylesheets.

Application Launcher

The top navigation bar also contains an optional application launcher for linking to other web applications. This dropdown menu is empty by default, but when links are added, appears to the left of the help menu in the masthead.

  1. // Add items to the application launcher dropdown menu.
  2. window.OPENSHIFT_CONSTANTS.APP_LAUNCHER_NAVIGATION = [{
  3.   title: "Dashboard",                    // The text label
  4.   iconClass: "fa fa-dashboard",          // The icon you want to appear
  5.   href: "http://example.com/dashboard",  // Where to go when this item is clicked
  6.   tooltip: 'View dashboard'              // Optional tooltip to display on hover
  7. }, {
  8.   title: "Manage Account",
  9.   iconClass: "pficon pficon-user",
  10.   href: "http://example.com/account",
  11.   tooltip: "Update email address or password."
  12. }];

Add the script as described in Loading Extension Scripts and Stylesheets.

System Status Badge

The top navigation bar can also include an optional system status badge in order to notify users of system-wide events such as maintenance windows. To make use of the existing styles using a yellow warning icon for the badge, follow the example below.

  1. 'use strict';
  3. angular
  4.   .module('mysystemstatusbadgeextension', ['openshiftConsole'])
  5.   .run([
  6.     'extensionRegistry',
  7.     function(extensionRegistry) {
  8.       // Replace http://status.example.com/ with your domain
  9.       var system_status_elem = $('<a href="http://status.example.com/"' +
  10.       'target="_blank" class="nav-item-iconic system-status"><span title="' +
  11.       'System Status" class="fa status-icon pficon-warning-triangle-o">' +
  12.       '</span></a>');
  14.       // Add the extension point to the registry so the badge appears
  15.       // To disable the badge, comment this block out
  16.       extensionRegistry
  17.         .add('nav-system-status', function() {
  18.           return [{
  19.             type: 'dom',
  20.             node: system_status_elem
  21.           }];
  22.         });
  23.     }
  24.   ]);
  26. hawtioPluginLoader.addModule('mysystemstatusbadgeextension');

Add the script as described in Loading Extension Scripts and Stylesheets.

Project Left Navigation

When navigating within a project, a menu appears on the left with primary and secondary navigation. This menu structure is defined as a constant and can be overridden or modified.

Significant customizations to the project navigation may affect the user experience and should be done with careful consideration. You may need to update this customization in future upgrades if you modify existing navigation items.

  1. // Append a new primary nav item.  This is a simple direct navigation item
  2. // with no secondary menu.
  3. window.OPENSHIFT_CONSTANTS.PROJECT_NAVIGATION.push({
  4.   label: "Dashboard",           // The text label
  5.   iconClass: "fa fa-dashboard", // The icon you want to appear
  6.   href: "/dashboard"            // Where to go when this nav item is clicked.
  7.                                 // Relative URLs are pre-pended with the path
  8.                                 // '/project/<project-name>'
  9. });
  11. // Splice a primary nav item to a specific spot in the list.  This primary item has
  12. // a secondary menu.
  13. window.OPENSHIFT_CONSTANTS.PROJECT_NAVIGATION.splice(2, 0, { // Insert at the third spot
  14.   label: "Git",
  15.   iconClass: "fa fa-code",
  16.   secondaryNavSections: [       // Instead of an href, a sub-menu can be defined
  17.     {
  18.       items: [
  19.         {
  20.           label: "Branches",
  21.           href: "/git/branches",
  22.           prefixes: [
  23.             "/git/branches/"     // Defines prefix URL patterns that will cause
  24.                                  // this nav item to show the active state, so
  25.                                  // tertiary or lower pages show the right context
  26.           ]
  27.         }
  28.       ]
  29.     },
  30.     {
  31.       header: "Collaboration",   // Sections within a sub-menu can have an optional header
  32.       items: [
  33.         {
  34.           label: "Pull Requests",
  35.           href: "/git/pull-requests",
  36.           prefixes: [
  37.             "/git/pull-requests/"
  38.           ]
  39.         }
  40.       ]
  41.     }
  42.   ]
  43. });
  45. // Add a primary item to the top of the list.  This primary item is shown conditionally.
  46. window.OPENSHIFT_CONSTANTS.PROJECT_NAVIGATION.unshift({
  47.   label: "Getting Started",
  48.   iconClass: "pficon pficon-screen",
  49.   href: "/getting-started",
  50.   prefixes: [                   // Primary nav items can also specify prefixes to trigger
  51.     "/getting-started/"         // active state
  52.   ],
  53.   isValid: function() {         // Primary or secondary items can define an isValid
  54.     return isNewUser;           // function. If present it will be called to test whether
  55.                                 // the item should be shown, it should return a boolean
  56.   }
  57. });
  59. // Modify an existing menu item
  60. var applicationsMenu = _.find(window.OPENSHIFT_CONSTANTS.PROJECT_NAVIGATION, { label: 'Applications' });
  61. applicationsMenu.secondaryNavSections.push({ // Add a new secondary nav section to the Applications menu
  62.   // my secondary nav section
  63. });

Add the script as described in Loading Extension Scripts and Stylesheets.

Configuring Featured Applications

The web console has an optional list of featured application links in its landing page catalog. These appear near the top of the page and can have an icon, a title, a short description, and a link.

Featured Applications

  1. // Add featured applications to the top of the catalog.
  2. window.OPENSHIFT_CONSTANTS.SAAS_OFFERINGS = [{
  3.   title: "Dashboard",                         // The text label
  4.   icon: "fa fa-dashboard",                    // The icon you want to appear
  5.   url: "http://example.com/dashboard",        // Where to go when this item is clicked
  6.   description: "Open application dashboard."  // Short description
  7. }, {
  8.   title: "System Status",
  9.   icon: "fa fa-heartbeat",
  10.   url: "http://example.com/status",
  11.   description: "View system alerts and outages."
  12. }, {
  13.   title: "Manage Account",
  14.   icon: "pficon pficon-user",
  15.   url: "http://example.com/account",
  16.   description: "Update email address or password."
  17. }];

Add the script as described in Loading Extension Scripts and Stylesheets.

Configuring Catalog Categories

Catalog categories organize the display of items in the web console catalog landing page. Each category has one or more subcategories. A builder image, template, or service is grouped in a subcategory if it includes a tag listed in the matching subcategory tags, and an item can appear in more than one subcategory. Categories and subcategories only display if they contain at least one item.

Significant customizations to the catalog categories may affect the user experience and should be done with careful consideration. You may need to update this customization in future upgrades if you modify existing category items.

  1. // Find the Languages category.
  2. var category = _.find(window.OPENSHIFT_CONSTANTS.SERVICE_CATALOG_CATEGORIES,
  3.                       { id: 'languages' });
  4. // Add Go as a new subcategory under Languages.
  5. category.subCategories.splice(2,0,{ // Insert at the third spot.
  6.   // Required. Must be unique.
  7.   id: "go",
  8.   // Required.
  9.   label: "Go",
  10.   // Optional. If specified, defines a unique icon for this item.
  11.   icon: "icon-go-gopher",
  12.   // Required. Items matching any tag will appear in this subcategory.
  13.   tags: [
  14.     "go",
  15.     "golang"
  16.   ]
  17. });
  19. // Add a Featured category as the first category tab.
  20. window.OPENSHIFT_CONSTANTS.SERVICE_CATALOG_CATEGORIES.unshift({
  21.   // Required. Must be unique.
  22.   id: "featured",
  23.   // Required
  24.   label: "Featured",
  25.   subCategories: [
  26.     {
  27.       // Required. Must be unique.
  28.       id: "go",
  29.       // Required.
  30.       label: "Go",
  31.       // Optional. If specified, defines a unique icon for this item.
  32.       icon: "icon-go-gopher",
  33.       // Required. Items matching any tag will appear in this subcategory.
  34.       tags: [
  35.         "go",
  36.         "golang"
  37.       ]
  38.     },
  39.     {
  40.       // Required. Must be unique.
  41.       id: "jenkins",
  42.       // Required.
  43.       label: "Jenkins",
  44.       // Optional. If specified, defines a unique icon for this item.
  45.       icon: "icon-jenkins",
  46.       // Required. Items matching any tag will appear in this subcategory.
  47.       tags: [
  48.         "jenkins"
  49.       ]
  50.     }
  51.   ]
  52. });

Add the script as described in Loading Extension Scripts and Stylesheets.

Configuring Quota Notification Messages

Whenever a user reaches a quota, a quota notification is put into the notification drawer. A custom quota notification message, per quota resource type, can be added to the notification. For example:

  1. Your project is over quota. It is using 200% of 2 cores CPU (Limit). Upgrade
  2. to <a href='https://www.openshift.com'>OpenShift Online Pro</a> if you need
  3. additional resources.

The “Upgrade to…​” part of the notification is the custom message and may contain HTML such as links to additional resources.

Since the quota message is HTML markup, any special characters need to be properly escaped for HTML.

Set the window.OPENSHIFT_CONSTANTS.QUOTA_NOTIFICATION_MESSAGE property in an extension script to customize the message for each resource.

  1. // Set custom notification messages per quota type/key
  2. window.OPENSHIFT_CONSTANTS.QUOTA_NOTIFICATION_MESSAGE = {
  3.   'pods': 'Upgrade to <a href="https://www.openshift.com">OpenShift Online Pro</a> if you need additional resources.',
  4.   'limits.memory': 'Upgrade to <a href="https://www.openshift.com">OpenShift Online Pro</a> if you need additional resources.'
  5. };

Add the script as described in Loading Extension Scripts and Stylesheets.

Configuring the Create From URL Namespace Whitelist

Create from URL only works with image streams or templates from namespaces that have been explicitly specified in OPENSHIFT_CONSTANTS.CREATE_FROM_URL_WHITELIST. To add namespaces to the whitelist, follow these steps:

openshift is included in the whitelist by default. Do not remove it.

  1. // Add a namespace containing the image streams and/or templates
  2. window.OPENSHIFT_CONSTANTS.CREATE_FROM_URL_WHITELIST.push(
  3.   'shared-stuff'
  4. );

Add the script as described in Loading Extension Scripts and Stylesheets.

Disabling the Copy Login Command

The web console allows users to copy a login command, including the current access token, to the clipboard from the user menu and the Command Line Tools page. This function can be changed so that the user’s access token is not included in the copied command.

  1. // Do not copy the user's access token in the copy login command.
  2. window.OPENSHIFT_CONSTANTS.DISABLE_COPY_LOGIN_COMMAND = true;

Add the script as described in Loading Extension Scripts and Stylesheets.

Enabling Wildcard Routes

If you enabled wildcard routes for a router, you can also enable wildcard routes in the web console. This lets users enter hostnames starting with an asterisk like *.example.com when creating a route. To enable wildcard routes:

  1. window.OPENSHIFT_CONSTANTS.DISABLE_WILDCARD_ROUTES = false;

Add the script as described in Loading Extension Scripts and Stylesheets.

Learn how to configure HAProxy routers to allow wildcard routes.

Customizing the Login Page

You can also change the login page, and the login provider selection page for the web console. Run the following commands to create templates you can modify:

  1. $ oc adm create-login-template > login-template.html
  2. $ oc adm create-provider-selection-template > provider-selection-template.html

Edit the file to change the styles or add content, but be careful not to remove any required parameters inside the curly brackets.

To use your custom login page or provider selection page, set the following options in the master configuration file:

  1. oauthConfig:
  2.   ...
  3.   templates:
  4.     login: /path/to/login-template.html
  5.     providerSelection: /path/to/provider-selection-template.html

Relative paths are resolved relative to the master configuration file. You must restart the server after changing this configuration.

When there are multiple login providers configured or when the alwaysShowProviderSelection option in the master-config.yaml file is set to true, each time a user’s token to OKD expires, the user is presented with this custom page before they can proceed with other tasks.

Example Usage

Custom login pages can be used to create Terms of Service information. They can also be helpful if you use a third-party login provider, like GitHub or Google, to show users a branded page that they trust and expect before being redirected to the authentication provider.

Customizing the OAuth Error Page

When errors occur during authentication, you can change the page shown.

  1. Run the following command to create a template you can modify:

    1. $ oc adm create-error-template > error-template.html

  2. Edit the file to change the styles or add content.

    You can use the Error and ErrorCode variables in the template. To use your custom error page, set the following option in the master configuration file:

    1. oauthConfig:
    2.   ...
    3.   templates:
    4.     error: /path/to/error-template.html

    Relative paths are resolved relative to the master configuration file.

  3. You must restart the server after changing this configuration.

Changing the Logout URL

You can change the location a console user is sent to when logging out of the console by modifying the clusterInfo.logoutPublicURL parameter in the webconsole-config ConfigMap.

  1. $ oc edit configmap/webconsole-config -n openshift-web-console

Here is an example that changes the logout URL to [https://www.example.com/logout](https://www.example.com/logout):

  1. apiVersion: v1
  2. kind: ConfigMap
  3. data:
  4.   webconsole-config.yaml: |
  5.     apiVersion: webconsole.config.openshift.io/v1
  6.     clusterInfo:
  7.       [...]
  8.       logoutPublicURL: "https://www.example.com/logout"
  9.     [...]

This can be useful when authenticating with Request Header and OAuth or OpenID identity providers, which require visiting an external URL to destroy single sign-on sessions.

Configuring Web Console Customizations with Ansible

During cluster installations, many modifications to the web console can be configured using the following parameters, which are configurable in the inventory file:

Example Web Console Customization with Ansible

  1. # Configure `clusterInfo.logoutPublicURL` in the web console configuration
  2. # See: https://docs.openshift.com/enterprise/latest/install_config/web_console_customization.html#changing-the-logout-url
  3. #openshift_master_logout_url=https://example.com/logout
  5. # Configure extension scripts for web console customization
  6. # See: https://docs.openshift.com/enterprise/latest/install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets
  7. #openshift_web_console_extension_script_urls=['https://example.com/scripts/menu-customization.js','https://example.com/scripts/nav-customization.js']
  9. # Configure extension stylesheets for web console customization
  10. # See: https://docs.openshift.com/enterprise/latest/install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets
  11. #openshift_web_console_extension_stylesheet_urls=['https://example.com/styles/logo.css','https://example.com/styles/custom-styles.css']
  13. # Configure a custom login template in the master config
  14. # See: https://docs.openshift.com/enterprise/latest/install_config/web_console_customization.html#customizing-the-login-page
  15. #openshift_master_oauth_templates={'login': '/path/to/login-template.html'}
  17. # Configure `clusterInfo.metricsPublicURL` in the web console configuration for cluster metrics. Ansible is also able to configure metrics for you.
  18. # See: https://docs.openshift.com/enterprise/latest/install_config/cluster_metrics.html
  19. #openshift_master_metrics_public_url=https://hawkular-metrics.example.com/hawkular/metrics
  21. # Configure `clusterInfo.loggingPublicURL` in the web console configuration for aggregate logging. Ansible is also able to install logging for you.
  22. # See: https://docs.openshift.com/enterprise/latest/install_config/aggregate_logging.html
  23. #openshift_master_logging_public_url=https://kibana.example.com

Changing the Web Console URL Port and Certificates

To ensure your custom certificate is served when users access the web console URL, add the certificate and URL to the namedCertificates section of the master-config.yaml file. See Configuring Custom Certificates for the Web Console or CLI for more information.

To set or modify the redirect URL for the web console, modify the openshift-web-console oauthclient:

  1. $ oc edit oauthclient openshift-web-console

To ensure users are correctly redirected, update the PublicUrls for the openshift-web-console configmap:

  1. $ oc edit configmap/webconsole-config -n openshift-web-console

Then, update the value for consolePublicURL.