Skip to content

Wpb 26240 - #122

Merged
julialongtin merged 8 commits into
mainfrom
WPB-26240
Jul 30, 2026
Merged

Wpb 26240#122
julialongtin merged 8 commits into
mainfrom
WPB-26240

Conversation

@julialongtin

@julialongtin julialongtin commented Jul 30, 2026

Copy link
Copy Markdown
Member

Change type

  • Documentation change
  • Build pipeline change
  • Submodule update
  • Deployment change

Basic information

  • THIS CHANGE REQUIRES A WIRE-DOCS RELEASE NOW

Testing

  • I ran/applied the changes myself, in a test environment.

Tracking

  • I mentioned this PR in Jira, OR I mentioned the Jira ticket in this PR.
  • I mentioned this PR in one of the issues attached to one of our repositories.

@julialongtin
julialongtin requested review from a team as code owners July 30, 2026 13:27
Comment thread src/how-to/upgrade/config-references/wire-server-5.32.0.md Outdated

@Veki301 Veki301 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, add the link for the config-references/wire-server-5.32.0.md into 05-config-reference.md

Comment thread src/understand/overview.md Outdated
![image](img/calling-DMZ.svg)

In the above diagram, we have routed and labeled the calling traffic into a non-federated Wire calling cluster. As you can see, placing calling in it's own kubernetes cluster is much safer, as the cluster does not have access to any of the wire databases. For most configurations, the calling cluster and the wire backend do not need to speak at all.
In the above diagram, we have routed and labeled the calling traffic into a non-federated Wire calling cluster. A Wire Calling Cluster is typically placed in an DMZ, where the users can reach it, but the Mire Messaging Cluster cannot. Wire As you can see, placing calling in it's own kubernetes cluster is much safer, as the cluster does not have access to any of the Wire databases. For most configurations, the calling cluster and the Wire backend do not need to speak at all.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mire Messaging Cluster

@Veki301 Veki301 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@julialongtin
julialongtin merged commit 46e8d87 into main Jul 30, 2026
2 checks passed
Comment thread mkdocs.yml
- Wire Server 5.28: how-to/upgrade/config-references/wire-server-5.28.0.md
- Wire Server 5.29: how-to/upgrade/config-references/wire-server-5.29.0.md
- Wire Server 5.30: how-to/upgrade/config-references/wire-server-5.30.0.md
- Wire Server 5.30: how-to/upgrade/config-references/wire-server-5.32.0.md

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Wire Server 5.30: how-to/upgrade/config-references/wire-server-5.32.0.md
- Wire Server 5.32: how-to/upgrade/config-references/wire-server-5.32.0.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants