centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-30: Updated architecture diagram, removed mention of anonymous data collection after removal of Matomo

Browse Source
This commit is contained in:
James Carppe
2026-03-09 00:45:57 +00:00
committed by gitbook-bot
parent 692e8e7592
commit 175fb2be1d
2 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
.gitbook/assets/2.38-portainer-architecture-detailed.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 304 KiB

4
start/architecture.md
View File

@@ -16,7 +16,7 @@ For a deeper dive into the architecture of Portainer, have a look at our [techni
A single Portainer Server will accept connections from any number of Portainer Agents, providing the ability to manage multiple clusters from one centralized interface. To do this, the Portainer Server container requires data persistence. The Portainer Agents are stateless, with data being shipped back to the Portainer Server container.
<figure><img src="../.gitbook/assets/2.33-portainer-architecture-detailed.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/2.38-portainer-architecture-detailed.png" alt=""><figcaption></figcaption></figure>
{% hint style="info" %}
We don't currently support running multiple instances of the Portainer Server container to manage the same clusters. We recommend running the Portainer Server on a specific management node, with Portainer Agents deployed across the remaining nodes.
@@ -34,8 +34,6 @@ The classic Agent option remains for legacy purposes, and can still be used for
Portainer runs exclusively on your servers, within your network, behind your own firewalls. As a result, we do not currently hold any SOC or PCI/DSS compliance because we do not host any of your infrastructure. You can even run Portainer completely disconnected (air-gapped) without any impact on functionality.
While we do (optionally) collect anonymous usage analytics from Portainer installations, we remain compliant with GDPR. Data collection can be disabled when you install the product, or at any time after that. If your installation is air-gapped, collection will silently fail without any adverse effects.
{% content-ref url="lifecycle.md" %}
[lifecycle.md](lifecycle.md)
{% endcontent-ref %}