Describe the enhancement:
Add support to Fleet Server for offering package/executable updates to OpAMP clients. This is the most complex capability — it requires integration with an upstream upgrade process, package signing/verification, and a delivery mechanism for binaries. Lowest priority / optional for this outcome.
Capability advertisement vs. offering:
Per the OpAMP spec, Fleet Server MUST advertise OffersPackages in the capabilities field of the first ServerToAgent message unconditionally. However, Fleet Server MUST NOT actually send a PackagesAvailable payload unless the client has advertised AcceptsPackages in its most recent AgentToServer message. Advertisement is unconditional; offering is gated on client capability. See the Packages section of the spec.
Testing:
⚠️ This feature cannot currently be tested end-to-end with the upstream OTel Collector supervisor. The supervisor has no config key for accepts_packages and does not advertise the capability bit. Testing will require upstream supervisor support (tracked at opentelemetry-collector-contrib#47272). See the OpAMP Supervisor README and the OTel Collector contrib releases page.
Describe a specific use case for the enhancement or feature:
Fleet centrally offers package/executable updates to managed OpAMP agents, enabling operators to upgrade agent binaries across a fleet from Fleet rather than managing host-level package installs.
Describe the enhancement:
Add support to Fleet Server for offering package/executable updates to OpAMP clients. This is the most complex capability — it requires integration with an upstream upgrade process, package signing/verification, and a delivery mechanism for binaries. Lowest priority / optional for this outcome.
Capability advertisement vs. offering:
Per the OpAMP spec, Fleet Server MUST advertise
OffersPackagesin thecapabilitiesfield of the firstServerToAgentmessage unconditionally. However, Fleet Server MUST NOT actually send aPackagesAvailablepayload unless the client has advertisedAcceptsPackagesin its most recentAgentToServermessage. Advertisement is unconditional; offering is gated on client capability. See the Packages section of the spec.Testing:
accepts_packagesand does not advertise the capability bit. Testing will require upstream supervisor support (tracked at opentelemetry-collector-contrib#47272). See the OpAMP Supervisor README and the OTel Collector contrib releases page.Describe a specific use case for the enhancement or feature:
Fleet centrally offers package/executable updates to managed OpAMP agents, enabling operators to upgrade agent binaries across a fleet from Fleet rather than managing host-level package installs.