From 98fbbae0acd51b1d1a223c5e4ba57275bb83347d Mon Sep 17 00:00:00 2001 From: James Carppe Date: Mon, 9 Mar 2026 00:52:33 +0000 Subject: [PATCH] GITBOOK-11: Updated diagram and link on architecture FAQ --- faqs/getting-started/what-is-portainers-architecture.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/faqs/getting-started/what-is-portainers-architecture.md b/faqs/getting-started/what-is-portainers-architecture.md index 24516504..d8774442 100644 --- a/faqs/getting-started/what-is-portainers-architecture.md +++ b/faqs/getting-started/what-is-portainers-architecture.md @@ -7,9 +7,10 @@ metaLinks: # What is Portainer's architecture? -Portainer consists of two elements: the Portainer Server and the Portainer Agent. Both run as lightweight containers on your existing containerized infrastructure. The Portainer Agent should be deployed to each node in your cluster and configured to report back to the Portainer Server container.\ +Portainer consists of two elements: the Portainer Server and the Portainer Agent. Both run as lightweight containers on your existing containerized infrastructure. The Portainer Agent should be deployed to each node in your cluster and configured to report back to the Portainer Server container. + 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. -
+
-For a deeper dive into the architecture of Portainer, have a look at our [reference architecture](https://academy.portainer.io/architecture). +For a deeper dive into the architecture of Portainer, have a look at our [technical architecture overview](https://dl.portainer.io/dl/whitepapers/portainer-technical-architecture.pdf).