Skip to content

W-17971776-Egress-rule-port #384

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

Open
luanamulesoft wants to merge 1 commit into
base: latest
Choose a base branch
from
Open

W-17971776-Egress-rule-port #384

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
14 changes: 14 additions & 0 deletions cloudhub-2/modules/ROOT/pages/ps-config-app-level-egress.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,20 @@ You can apply the application-level egress rules that you configured in your pri
. In the *Egress Rule Group* section, select the ruleset to apply to your application.
. Click *Apply Changes*.

== Application Clustering and Egress Rules

Application clustering in CloudHub 2.0 requires replicas to discover each other via Hazelcast. For clustered applications that use application-level egress rules, add an egress rule that allows this traffic.

[IMPORTANT]
====
Add an application-level egress rule that allows traffic to the local private network on port 5701. Without this rule, replicas can't discover or join the Hazelcast cluster, and clustering fails.
Add this rule to the egress rule group for your clustered application:
* *Protocol*: `TCP`
* *Destination*: `Local private network`
* *Port*: `5701`
====

== Configure an Application-Level Egress Connection to Anypoint MQ

Expand Down