From 165b7df3f4ef480484242692ecf0e60dc95975a5 Mon Sep 17 00:00:00 2001 From: LewisKSaint Date: Tue, 25 Jun 2024 15:34:51 -0400 Subject: [PATCH] DATAGO-76030 | docs update on openshift routes --- docs/PubSubPlusOpenShiftDeployment.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/PubSubPlusOpenShiftDeployment.md b/docs/PubSubPlusOpenShiftDeployment.md index 5cc08ab..5bc0bc1 100644 --- a/docs/PubSubPlusOpenShiftDeployment.md +++ b/docs/PubSubPlusOpenShiftDeployment.md @@ -200,6 +200,8 @@ The principles for exposing services that are described in the [Solace PubSub+ E The following sections provide examples for each router type. Replace `` with the name of the service of your deployment. The port name must match the `service.ports` name in the PubSub+ `values.yaml` file. Additional services can be exposed by an additional route for each. +> Note: When configuring Routes to connect two PubSub+ Event Broker services for [Message VPN Bridges](https://docs.solace.com/Features/VPN/Message-VPN-Bridges-Overview.htm), the service needs to be accessible from every other PubSub+ Event Broker service. + ##### HTTP With No TLS The following commands create an HTTP route to the REST service at path `/`: