Getting started

Red Hat Service Interconnect 1.5

Using the CLI and YAML

Abstract

This guide describes how to get started with Red Hat Service Interconnect 1.5.
Red Hat Service Interconnect is a Red Hat build of the open source Content from skupper.io is not included.Skupper project.

Chapter 1. Getting started with the CLI

The Skupper CLI allows you create sites and expose services on the service network.

Prerequisites

Procedure

  1. Check the version of the CLI using the following command: 

    $ skupper version
client version 1.5.<minor>-redhat-<build-number>

    The Red Hat build of the skupper CLI includes redhat in the version displayed.

  2. Perform an appropriate tutorial from the Examples, for example, 'Hello World'.
Note

If you create a site in an OpenShift Container Platform version 4.11 or 4.12 namespace, a message starting with the following warning is displayed:

W0320 15:27:27.446084 48301 warnings.go:70] would violate PodSecurity "restricted:v1.24"

You can ignore this message as it relates to a future restriction in OpenShift.

Chapter 2. Getting started with YAML

Using YAML files to configure Skupper allows you to use source control to track and manage Skupper network changes.

Prerequisites

Procedure

  1. Create a site as described in Content from skupper.io is not included.Creating a Skupper site using YAML.

    Note

    You can use the same YAML to create a site whether you installed Red Hat Service Interconnect using the Operator or by installing the skupper controller.

  2. Link sites using the skupper command.

    Note

    While it is possible to create and use tokens using YAML, the process is procedural rather than declarative.

  3. Expose services as described in Content from skupper.io is not included.Configuring services using annotations.

Chapter 3. Resources

The following resources are available:

Chapter 4. Creating a core dump on OpenShift 4

If you encounter issues on OpenShift 4, Red Hat support might ask for core dumps from your cluster. To create a core dump, see Gathering a CRI-O Core Dump on Red Hat CoreOS in OCP 4.

Appendix A. About Service Interconnect documentation

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.

Revised on 2024-08-14 15:50:16 UTC

Legal Notice

Copyright © 2024 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 Content from creativecommons.org is not included.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.