Let's Learn Portainer.
A twelve-module training course on Portainer Business Edition; you follow along in your own lab. Written for integrators, platform engineers, architects, and buyers who need to install, configure, defend, and operate Portainer in production environments.
What this course is
This exists because partners, integrators, and enterprise buyers keep asking the same questions about how Portainer is built, what it does, and how it fits into their operating model. Rather than answer them one at a time, we wrote this. It runs top to bottom, module by module, and you follow along in your own lab.
The tone is educator to peer. We assume you know what a container is, that Kubernetes exists, and that you have deployed things before; we do not assume you know Portainer, and we do not assume you know how to operate a container platform at scale for a real business.
Who this is for
You are the audience if you are any of the following:
- A partner or integrator preparing to sell, install, or support Portainer in customer environments.
- A platform engineer or architect evaluating Portainer for your own organization.
- A CIO or CISO working out whether the operator control plane category is the right shape for your Kubernetes and container estate.
If you are just curious about Portainer as a self-hosted homelab tool, most of this will still be useful.
By the last module, you should be able to install and configure Portainer Business Edition for production, onboard multiple environments, tune it for your operating model, and know how to keep it running over time; you should also be able to defend the choice of Portainer to a technical audience.
The twelve-module roadmap
The first three modules set the argument for why Portainer exists and what it is; modules four to six walk through deployment, configuration, and environment onboarding; modules seven through ten cover the four heaviest capability surfaces (identity, fleet, GitOps, observability); modules eleven and twelve cover the add-on model and how you operate Portainer once it is running.
Why Portainer exists
The operational debt that arrived with containers; the eight projects hidden inside a "container platform"; the three phases of platform work; the twelve tools you would otherwise assemble; the operator control plane thesis; a note on CE.
What a Container Management Platform is
What sits above the runtime; Docker versus Kubernetes; where Portainer fits in the seven-layer stack; what Portainer deliberately does not solve.
Portainer architecture
The Management Server; the Portainer Agent; the Edge Agent (standard); the Edge Agent (async); tunnels, polling, and trust; the datastore; when to choose which agent mode.
Deploy a Portainer Management Server
Runtime choice and sizing; persistent storage; dedicated versus shared management environments; the first-boot admin flow; adding your license.
Configure for enterprise use
SSL and TLS; ports and firewalls; scheduled backup to S3/Azure Blob; LDAP, Active Directory, and OAuth; teams before users; feature flags.
Onboard environments
Docker Standalone, Docker Swarm, existing Kubernetes; provisioning KubeSolo; Talos through Sidero Omni; adding managed Kubernetes (AKS, EKS, GKE); trust and access.
Identity and access
The identity model; users, teams, and roles; environment groups as tenancy boundaries; the Kubernetes API proxy that turns Portainer into an authenticated kubectl endpoint; audit trail; where Vault and External Secrets Operator fit.
Fleet Management
Environment groups, edge groups, and tags; edge compute (edge stacks, jobs, and configurations); the policy engine and how it enforces; distribution to mixed and async fleets; registry governance as fleet policy; where Kyverno, OPA, and Falco sit alongside.
GitOps deployments
Sources and workflows; polling and webhooks; templates and catalog; change windows and ITSM alignment; how Portainer's GitOps differs from Argo CD and Flux, and where they coexist.
Observability and Day-2 operations
The embedded Prometheus and Alertmanager; agent-side rule evaluation for edge; notification receivers; SIEM export; the day-2 operator surface (containers, pods, exec sessions, logs); where Datadog, Dynatrace, Splunk, and OneUptime fit.
Portainer add-ons
The catalog; Helm-based lifecycle; the reverse-proxy gateway; the machine API; how Portainer-Run installs as an add-on.
Operating Portainer
Backup and restore; auto-patch on the LTS line; license renewal and node counting; disaster recovery scenarios; the common failure modes and how to triage them.
What you'll need for the lab
This is a read-along course that has prompts for following along to set Portainer up yourself. So before you start Module 4, get the lab together.
To work with this training, you will need to provide a minimum of 4 VMs, ideally 7, and if you want to learn management of Cloud KaaS (AKS/EKS/GKE) you will also need to deploy a cluster there.
The four-VM path lets you stand up a Portainer Management Server, then onboard three environments - one Kubernetes, one Docker Standalone, and one Docker Swarm - so you get to touch every environment type Portainer manages. The seven-VM path adds spare hosts for Docker Swarm managers (three is the working minimum for a real Swarm), and gives you a second Kubernetes environment to practice fleet operations against more than one cluster.
Adding a KaaS cluster (AKS, EKS, or GKE) is only necessary if you want to work through the KaaS onboarding path in Module 6 and see how Portainer treats a managed cluster against a self-managed one. It is not required to complete the course; it is useful if you use managed Kubernetes, which most enterprises do.
Nothing in this course requires physical hardware. VMs on your laptop, on a home lab hypervisor, or in a public cloud project all work; specifics of what to install and how appear in Module 4 when you actually need them.
Start
Module 1 starts with the case for why Portainer exists at all; it is the shortest of the twelve and the one most likely to change how you frame the rest of the course. Read it before you do anything in your lab.
Start Module 1: Why Portainer exists