Introduction to Application Interconnect

Red Hat Application Interconnect 1.0

For Use with Application Interconnect 1.0 LIMITED AVAILABILITY


This guide introduces Red Hat Application Interconnect and describes a service network.


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.


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

Chapter 1. Overview of Application Interconnect

Application Interconnect introduces a service network, linking services across the hybrid cloud.

A service network enables communication between services running in different network locations. It allows geographically distributed services to connect as if they were all running in the same site.

This diagram shows a 'service network' connecting two Kubernetes clusters. The Skupper site in Namespace A, in the left cluster, has a deployment which exposes a TCP service to the service network. In the right cluster two sites can use that service as if the service existed in the right cluster.

For example, you can deploy your frontend in a public OpenShift cluster and deploy your backend in a private OpenShift cluster, then connect them into a service network.

A service network provides the following features:

  • Security by default. All inter-site traffic is protected by mutual TLS using a private, dedicated certificate authority (CA).
  • Easy connections between OpenShift clusters, even private clusters.
  • A service network supports existing TCP, HTTP1 or HTTP2-based applications without requiring modification.
  • Monitor your application traffic spread across multiple OpenShift clusters using the service network console.

You deploy and manage a service network using the skupper CLI.

Chapter 2. Application Interconnect documentation

The following titles are available:

Revised on 2022-06-24 16:32:53 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 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.