Using the Skupper console

Red Hat Application Interconnect 1.0

For Use with Application Interconnect 1.0 LIMITED AVAILABILITY

Abstract

This guide describes how to monitor Application Interconnect sites and a service network.

Preface

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Note

This Limited Availability release is not available to all customers. Contact Red Hat Sales if you are interested in learning more about Application Interconnect.

By default, when you create a Application Interconnect site, you also enable the Skupper console. The Skupper console URL is displayed whenever you check site status using skupper status.

Chapter 1. Accessing the Skupper console

By default, the Skupper console is available whenever you create a service network router and is protected by credentials available in the skupper-console-users secret.

Procedure

  1. Determine the Skupper console URL using the skupper CLI, for example:

    $ skupper status
    Skupper is enabled for namespace "west" in interior mode. It is not connected to any other sites. It has no exposed services.
    The site console url is:  https://skupper-west.apps-crc.testing
  2. Browse to the Skupper console URL. The credential prompt depends on how the site was created using skupper init:

    • using the --console-auth unsecured option, you are not prompted for credentials.
    • using the --console-auth openshift option, you are prompted to enter OpenShift cluster credentials.
    • using the default or --console-user <user> --console-password <password> options, you are prompted to enter those credentials.
  3. If you created the site using default settings, that is skupper init, a random password is generated for the admin user. To retrieve the password the admin user:

    $ kubectl get secret skupper-console-users -o jsonpath={.data.admin} | base64 -d
    JNZWzMHtyg

Chapter 2. Linking sites using the Skupper console

The Skupper console allows you create and use claim type tokens as described in Configuring Application Interconnect sites using the CLI.

Prerequisites

  • Two sites, each with Skupper console enabled
Procedure

Your browser may prompt you to allow using the clipboard. You must accept that prompt for this procedure.

  1. Log into the console for the first site.
  2. Navigate to Site in left hand menu.
  3. Click Link a remote site to display the steps for linking.
  4. Click Copy a token to the clipboard.
  5. Log into the console for the second site.
  6. Navigate to Site in left hand menu.
  7. Click Use a token to accept the token from the first site.
  8. Verify that the sites are linked by Checking that both sites are listed in the Network details section of the Site page.

Chapter 3. Exploring the Skupper console

The Skupper console provides an overview of the following:

  • Services - services that are exposed on the service network, both local and remote.
  • Sites - Application Interconnect installations on the current service network.
  • Deployments - deployments relating to exposed services.

The Skupper console also provides useful networking information about the service network, for example, traffic levels between sites.

skupper console
  1. Perform the Creating a service network with OpenShift tutorial.
  2. Navigate to the Skupper console.
  3. Click the Network menu item. Both the east and west sites should be displayed in circles.
  4. Drag and drop the west circle to be on the left of the east circle.
  5. Click the Table tab to display the sites as text items. This view allows you drill down into details relating to the selected site.
  6. Click the Deployments menu item. This view shows you any deployments that are exposed as services on the service network. In this case, the console displays the hello-world-backend (east) deployment.
  7. Click the Services menu item to display details for all services exposed on the service network.

    Note

    Although two services are involved in the tutorial, only one service, hello-world-backend is exposed on the service network.

  8. Click the Site menu. This page shows:

    • The number of sites in the service network.
    • The services that are exposed on the service network.
    • The gateways that are defined in the service network.
    • The traffic for the current site.

Revised on 2022-06-24 16:33:28 UTC

Legal Notice

Copyright © 2022 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.