3. Cluster Customizations (Blue)

3.0 User Access

Establish a shared project namespace that everyone on the team can use:

  1. Use an admin account to create a new project:

    oc new-project blue-team
  2. Provide existing user accounts with access to the blue-team project namespace:

    for user in {1..10}; do oc adm policy add-role-to-user edit user$user ; done

3.1 Console Notifications

  1. Click on the Import (represented by a plus sign, +) link in the web console header. Paste the following YAML into the text editing area:

    apiVersion: console.openshift.io/v1
    kind: ConsoleNotification
      name: hackathon-banner
      text: Welcome to the Blue Team OpenShift cluster for the Summit Connect Hackathon!
      location: BannerTop
        href: 'https://github.com/redhat-scholars/quickstart-workshop/tree/master/apps/blue'
        text: (View Source)
      color: white
      backgroundColor: blue
  2. Click Create to make the new ConsoleNotification visible to all cluster users

  1. Download an image to use for a header logo

  2. Store the image data in a Kubernetes configmap

    oc create configmap console-custom-logo --from-file /tmp/logo.png -n openshift-config
  3. Paste the following to create a YAML patch file. This file holds the updated cluster console operator configuration pointing to the console-custom-logo configmap:

    cat <<EOF > /tmp/patch.yaml
          key: logo.png
          name: console-custom-logo
  4. Patch the console operator configuration to apply the new logo:

    oc patch consoles.operator.openshift.io cluster --type merge --patch-file /tmp/patch.yaml

3.3 Configure Web Terminal

Update the cluster default terminal image by modifying the DevWorkspaceTemplate/web-terminal-tooling resource:

  1. Search All Projects for resources of type DevWorkspaceTemplate

    Search All Projects

    Search Resource type "DevWorkspaceTemplate"

  2. Select the resource named web-terminal-tooling

    View templates

  3. Click on YAML to modify the terminal settings

    web terminal tooling

  4. Add a new annotation after line 5:

    web-terminal.redhat.com/unmanaged-state: "true"
  5. Replace the spec.components[].container.image url with:

  6. Click Save to set the new default terminal image for the cluster

    web-terminal-tooling yaml config

  7. Close and restart your Web Terminal

  8. In a new terminal, check the version of the oc command line tool:

    oc version
    Client Version: 4.10.25
    Server Version: 4.10.26
    Kubernetes Version: v1.23.5+012e945

    If you don’t see an updated oc version, run the following command to refresh the web terminal tooling pod:

    oc delete pod -l 'controller.devfile.io/devworkspace_id'

    There will be a brief pause while the Web Terminal tooling container is replaced.

Non-admin users can also quickly override the default terminal image (without setting a new cluster default) using the wtoctl command:

wtoctl set image quay.io/ryan_j/summitconnect:latest

3.4 Installing a custom QuickStart

  1. Install the blue team quickstart, which guides you through provisioning Operators to manage a backend database and automate application connections to it:

  2. Open the QuickStarts catalog from the Help icon near the top right of the web console. Search the QuickStarts for the string "service binding" to filter the catalog until you find the QuickStart titled Summit Connect Hackathon - Service Binding.

  3. Click the QuickStart and follow the steps in it to deploy both tiers of a simple veterinary practice management application, the PetClinic.