Skip to main content
RunBook Academy

LinuxLI · Linux Fleet ArchitectureManagement plane

Fleet management plane - how a Linux fleet is operated

Foundation⏱ ~10 minbash

What you'll learn

  • Describe the fleet management plane
  • Identify the key components: identity, configuration, monitoring
  • Recognise the design principles
  • Choose a management stack

Prerequisites

Verified against Ubuntu 24.04 LTS · Debian 12 (Bookworm) · RHEL 9.x · Rocky Linux 9.x · AlmaLinux 9.x · Linux kernel 6.1 LTS / 6.6 LTS · systemd 255+ · OpenSSH 8.7p1 (RHEL 9) / 9.6p1 (Ubuntu 24.04) · nftables 1.0.x · chrony 4.x · Pacemaker 2.1.x · Corosync 3.1.x · 2026-08-09

Not yet marked complete on this device.

A Linux fleet is 10+ hosts operated as one. The management plane is the set of services that keep the fleet configured, secure, and observable. This lesson covers the architecture.

The management plane

Management plane
├── Identity (LDAP, AD, FreeIPA)
├── Configuration (Ansible, Puppet, Salt)
├── Secrets (Vault, KMS)
├── Monitoring (Prometheus, Grafana, Loki)
├── Logging (centralised)
├── Patching (apt, dnf, automation)
├── Backup (offsite, immutable)
└── Communication (chat, paging)

Each component is a service the fleet depends on. They themselves are Linux services that need to be reliable.

Design principles

  • Centralised: one source of truth for configuration, identity, secrets.
  • Version controlled: every change is in git.
  • Idempotent: applying the same configuration twice has the same effect.
  • Audited: who did what, when.
  • Reversible: rollback is a feature, not an afterthought.
  • Self-hosted or managed: choose based on operational capacity.

The components

Identity

  • FreeIPA: open-source identity with LDAP, Kerberos, DNS, certificate authority.
  • Active Directory: Microsoft; common in enterprises.
  • 389 Directory Server: open-source LDAP.
  • OpenLDAP: classic LDAP.
  • Keycloak: identity and access management with SSO.

For a Linux fleet, FreeIPA is the natural choice. AD works if the fleet is mixed with Windows.

Configuration

  • Ansible: agentless, YAML, large ecosystem. Best default.
  • Puppet: pull, agent, declarative.
  • Salt: pull or push, fast, complex.
  • Chef: pull, agent, Ruby.

For new designs, Ansible. For existing, stay with what works.

Secrets

  • HashiCorp Vault: open-source, dynamic secrets, policies.
  • AWS Secrets Manager: managed, KMS-integrated.
  • Azure Key Vault: managed, Azure-integrated.
  • GCP Secret Manager: managed, GCP-integrated.
  • sops + git: encrypted files in git.

For self-hosted, Vault. For cloud, the cloud provider’s secret manager.

Monitoring

  • Prometheus + Grafana: metrics + dashboards.
  • Loki: logs.
  • Tempo: traces.
  • OTel: unified pipeline.

See Part XLIV for details.

Self-hosted vs managed

Self-hostedManaged
Lower cost at scaleHigher cost, lower ops
Full controlVendor lock-in
Need to operateLess ops overhead
Customise freelyLimited by vendor

For most production, the management plane is self-hosted (Ansible, FreeIPA, Vault) on dedicated infrastructure. The data plane (workloads) is often cloud.

Knowledge check

Knowledge check · 3 questions

  1. Q1. Which tool is the natural choice for Linux fleet identity?

  2. Q2. The management plane is less important than the data plane.

  3. Q3. Which of the following are valid management plane components? Select all that apply.

Passing score: 75%. Answers are checked in this browser.