Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

v0.3.0

Compare
Choose a tag to compare
@bcwaldon bcwaldon released this 07 May 22:19
· 1875 commits to master since this release

New Features

  • Improved job state machine - see fleetctl load/unload and the fleetctl list-units STATE column
  • Support timer and path unit types
  • Add an X-ConditionMachineMetadata unit option (replaces --require flag)
  • Add an X-ConditionMachineID unit option (replaces X-ConditionMachineBootID option)
  • Add debug output to fleetctl
  • Assume .service extension if not provided in fleetctl commands

Major Bugs Fixed

  • #377: Cluster should not destroy itself during etcd leader election

Other Changes

  • Use machine ID instead of boot ID to identify Agents
  • Stop generating default peers of socket units
  • Stop publishing socket information with unit state
  • Stop calling 'enable' when starting unit under Agent

Upgrade Notes

While fleet is still under heavy development it is not reasonable to expect a seamless rolling upgrade of a fleet cluster. Do not expect a cluster to be usable with mixed versions of fleet, and do not expect old versions of fleetctl to work after the cluster has been upgraded.

An upgrade from v0.2 to v0.3 will not result in the loss of existing units, but any units that were active pre-upgrade may need to be be restarted post-upgrade. Using the new fleetctl binary, you can run fleetctl start --no-block on your units before beginning the upgrade to automatically transition them to a launched state once the upgrade is complete.