From 169d692ad273684be0c7ce284b706a6c6bdc3e56 Mon Sep 17 00:00:00 2001
From: schmidt-scaled <82834682+schmidt-scaled@users.noreply.github.com>
Date: Mon, 10 Aug 2026 21:29:55 +0200
Subject: [PATCH] docs: mark the monitoring stack as optional in the port table

The management node port table listed the monitoring stack next to the
mandatory services, so its ports read as required. Mark the row with a table
footnote stating that the stack is optional and that its ports only have to
be opened where it is deployed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 snippets/network-port-table.md | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/snippets/network-port-table.md b/snippets/network-port-table.md
index 8ba0c864..9c60c64c 100644
--- a/snippets/network-port-table.md
+++ b/snippets/network-port-table.md
@@ -1,14 +1,15 @@
-| Service              | Direction       | Hosts            | Network | Port(s)                         | Protocol(s)             |
-|----------------------|-----------------|------------------|---------|---------------------------------|-------------------------|
-| ICMP                 | egress          | control          | Control | -                               | ICMP                    |
-| storage-node-api     | egress          | storage          | Control | 5000                            | TCP                     |
-| NVMf (client-target) | egress          | client           | Storage | 4420-4499                       | TCP, UDP <sup>(1)</sup> |
-| FoundationDB         | ingress, egress | control          | Control | 4500                            | TCP                     |
-| control-plane-API    | ingress         | control          | Control | 80                              | TCP                     |
-| storage-node-RPC     | ingress, egress | storage, control | Control | 8080-9044                       | TCP                     |
-| Monitoring Stack     | ingress, egress | control          | Control | 12202, 13301, 13302, 9200, 9090 | TCP                     |
+| Service                         | Direction       | Hosts            | Network | Port(s)                         | Protocol(s)             |
+|---------------------------------|-----------------|------------------|---------|---------------------------------|-------------------------|
+| ICMP                            | egress          | control          | Control | -                               | ICMP                    |
+| storage-node-api                | egress          | storage          | Control | 5000                            | TCP                     |
+| NVMf (client-target)            | egress          | client           | Storage | 4420-4499                       | TCP, UDP <sup>(1)</sup> |
+| FoundationDB                    | ingress, egress | control          | Control | 4500                            | TCP                     |
+| control-plane-API               | ingress         | control          | Control | 80                              | TCP                     |
+| storage-node-RPC                | ingress, egress | storage, control | Control | 8080-9044                       | TCP                     |
+| Monitoring Stack <sup>(2)</sup> | ingress, egress | control          | Control | 12202, 13301, 13302, 9200, 9090 | TCP                     |
 
 <span style="font-size: 0.8em;">
 <sup>1</sup> The NVMf port range carries both transports. NVMe-oF/TCP uses it over TCP, NVMe-oF/RDMA
-over UDP. Only the protocol of the transport(s) in use has to be opened.
+over UDP. Only the protocol of the transport(s) in use has to be opened.<br>
+<sup>2</sup> The monitoring stack is optional. Its ports only have to be opened where it is deployed.
 </span>