Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DATAGO-76030 | docs update on openshift routes and solace bridges #54

Merged
merged 1 commit into from
Jun 25, 2024
Merged

DATAGO-76030 | docs update on openshift routes and solace bridges #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/PubSubPlusOpenShiftDeployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<my-pubsubplus-service>` 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 `/`:
Expand Down
Loading