Skip to main content

FleetAMP v0.2.0

Version 0.2.0 changes FleetAMP from collector-by-collector configuration into a group-governed fleet control plane.

Highlights​

  • Stable collector identity and richer inventory
  • Groups and delegated Group Owners
  • Section-based configuration policy
  • Latest-version editing with validate/preview and validate/save actions
  • Validation at authoring, submission, and approval
  • Assigned-reviewer approval queue with linked version diffs and mandatory change reasons
  • Admin-to-Admin or Admin-to-owning-Group-Owner review delegation
  • Request cancellation with retained, auditable history
  • Request status filtering, notifications, and expiry retention up to 90 days
  • Immutable deployment snapshots and automatic rollback
  • Desired/effective two-version drift view with report or enforce policy
  • Exact-match, group-scoped label deployment targeting
  • Admin, Group Owner, Operator, and Viewer roles
  • Expanded audit trail and page-level guidance

The UI is organized into Management, Instrumentation, Intelligence, Observe, and Administration. Blueprints, AI Insights, and MCP are visible as Upcoming so contributors can see the intended direction without confusing them with shipped functionality.

Compatibility and upgrade​

Back up v0.1 state before migration. Validate the upgrade in staging, confirm collector identity and group membership, and run an approval-to-rollback exercise before production. The v0.1 documentation is retained under Version history.

Licensing​

FleetAMP continues under the Apache License 2.0. See the repository LICENSE and NOTICE files for the authoritative terms and attribution requirements.

Planned after v0.2​

Reusable Blueprints and golden paths are planned for v0.3. Governance contracts and semantic-convention policy follow in v0.4, with intelligence, discovery, AI-assisted operations, and MCP integration in later milestones. See the roadmap for current sequencing.