Release Notes for Red Hat Application Interconnect 1.0

Red Hat Application Interconnect 1.0

Release Notes for Red Hat Application Interconnect 1.0 LIMITED AVAILABILITY

Abstract

These release notes contain the latest information about new features, enhancements, fixes, and issues contained in the Red Hat Application Interconnect 1.0 release.

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.

Chapter 1. New and changed features

This release of Red Hat Application Interconnect is incompatible with all previous releases of AMQ Interconnect 2.0. To avoid disruption, you must upgrade all sites in your service network to this release using the following command:

$ skupper update

1.1. Network status command

Use the skupper network status command to display an overview of the service network.

1.2. Red Hat Application Interconnect policy system

You can apply a policy system to restrict access to the service network as described in Securing a service network using policies.

1.3. TLS support for services using the HTTP2 protocol

Use the --enable-tls option to secure HTTP2 traffic between a backend pod and the Application Interconnect router pod.

1.4. Gateways

Red Hat recommends removing any gateways before upgrading, and recreating those gateways after a successful upgrade.

With this release only one gateway is created per user/host. Previously, a user could create multiple gateways, this is no longer possible. If you require multiple gateways per host, create a new user for each gateway.

Port negotiation limitation

If your protocol negotiates the communication port, for example active FTP, you cannot use that protocol to communicate across a service network.

1.5. Known issues

  • SKUPPER-274 - Skupper link site not working when using FIREFOX due to a missing function

    An error occurs if you try to link sites using the Firefox browser.

    Workaround

    Use the Chrome browser when creating links between sites using a browser.

  • SKUPPER-171 - Skupper policies don’t work on OCP 3.11

    You cannot apply the policy CRD to an OpenShift version 3.11 cluster.

    Workaround

    Upgrade OpenShift to version 4.

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