NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #808 by repository stars
Latest stable
v1.0.0
Last release 9 years ago
no release in 18 months
Ships unpredictably
gaps range from 1 weeks to 1.2 years
Nearly every release is documented
notes for 40 of 43 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
80 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Release from tag v1.0.0, commit b8127afc0 ("Merge pull request #1719 from jonboulle/master"), as of 2016-12-22.
Release from tag v1.0.0, commit b8127afc0 ("Merge pull request #1719 from jonboulle/master"), as of 2016-12-22.
Note that this is the final anticipated release of fleet and no future activity is planned. CoreOS will no longer sponsorship any continued maintenance or development of the project. If you are interested in the future of the project and wish to take over ownership, please contact fleet@coreos.com.
This release includes new features, especially gRPC communication, basic etcd authentication, and support for Install section. It also fixes numerous bugs that have been discovered recently. For details, please see the list below.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Release from tag v0.13.0, commit 1d6e74a5 ("Merge pull request #1572"), as of 2016-05-30.
Release from tag v0.13.0, commit 1d6e74a5 ("Merge pull request #1572"), as of 2016-05-30.
Nothing published for this version
Release from tag v0.12.0, commit e2a83700 ("Merge pull request #1544"), as of 2016-04-15.
Release from tag v0.12.0, commit e2a83700 ("Merge pull request #1544"), as of 2016-04-15.
## New Features - #1630: add support for etcd basic authentication
prefer key algorithm from known_hosts over the server's
Nothing published for this version
do not block forever waiting for global unit creation
correctly block waiting for unit creation in submit/load/start before proceeding with other actions
submit/load/start before proceeding with other actionsdestroyreworked race condition fix included in the last release. using consistent reads in fleetd for etcd was deemed too demanding, but watches don't work a
fix a race condition when creating units due to etcd reads without consistency
## Bugs fixed - #1301: fleetd 0.11.0 lacked default etcd endpoints. they have been restored, and defaults to http://127.0.0.1:2379 and http://127.0.0.
http://127.0.0.1:2379 and http://127.0.0.1:4001.## Bugs Fixed - #1273: prevent load/start of templates
Note that due to a change in the go version, the binaries for this release are not statically linked. Users in need of static fleetctl/fleetd binaries
Note that due to a change in the go version, the binaries for this release are not statically linked. Users in need of static fleetctl/fleetd binaries are recommended to upgrade to v0.11.0 or build fleet themselves.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
## Tweaks - #1205: set fleetctl flag --driver default to etcd is unset and --endpoint is etcd-like - #1204: communicate to end-user why fleet API unav
fleetctl flag --driver default to etcd is unset and --endpoint is etcd-like## New Features - #1034: use fleet API instead of etcd by default under fleetctl - #1084: identify global units in fleetctl list-unit-files - #1092 #1
fleetctl list-unit-filesfleetctl statussystemctl status## Bugs Fixed - #1158: lengthy deactivation prevents units from starting properly
## Bugs Fixed - #900, #977, #1003, #1127: failure of units to start due to "No such file or directory" error
The highlight of v0.9.0 is the finalization of the v1 API. From this point on, no backwards-incompatible changes will be made to the API specification
The highlight of v0.9.0 is the finalization of the v1 API. From this point on, no backwards-incompatible changes will be made to the API specification. The fleetctl tool will continue to communicate directly with etcd until a later release, at which time all etcd communication will be routed through the API endpoint of the fleetd daemon.
--ca-file, --key-file and --cert-file--ssh-timeoutfleetctl unloadfleetctl --help flagfleetctl --endpoint flag.json extension from discovery schema endpoint## Bugs Fixed - #933: prevent panic when attempting to steal engine lease - #937: lengthen lease on stolen lease to prevent racy handoff
## Bugs Fixed - #903: No longer block on systemd jobs (major case of "unkillable" units) - #910: Return proper HTTP status code when creating vs modif
## Bugs Fixed - #833: address "stuck" unit state - #867: validate acceptable unit names in both fleetctl and the API based on systemd's rules - #879:
fleetctl unloadssh, status and `journal with global unitsThe major new feature in this release is global units. These allow users to define units which will run on every agent in their fleet cluster. For ful
The major new feature in this release is global units. These allow users to define units which will run on every agent in their fleet cluster. For full details, see the unit files and scheduling documentation.
X- and X-Condition prefixes of certain unit options are now deprecated and should be removed from unit filesfleet binary is now called fleetd. Users may need to adjust their init scripts appropriately.TMACHINE field in fleetctl output has been renamed to TARGET. The old name will still function but is deprecated; users should migrate to TARGET## Bugs Fixed - #646: serialize systemd operations within a single fleet agent - #783: use TTLs to clean up stale state in etcd
The fleet engine no longer uses bidding to schedule work to the cluster. This caused a lot of unnecessary stress on etcd and was not able to quickly s
The fleet engine no longer uses bidding to schedule work to the cluster. This caused a lot of unnecessary stress on etcd and was not able to quickly schedule units into the cluster. This mechanism was replaced with a monolithic scheduler running in a single engine. Each engine master-elects this responsibility to provide quick failover in the event of a single machine going down.
We made a great amount of progress on fleet’s HTTP API. Its current resource layout will likely be what is released as the official API.
The relationship between unit state and the underlying fleet agents has been modified to allow multiple agents to report state under the same unit name. This change not only helps communicate what is actually happening in the cluster at any given time, but paves the way for global units (https://github.com/coreos/fleet/issues/681). This did have some consequences for fleetctl - the state and dstate fields moved from list-units to list-unit-files.
Unit signing has been removed. The related flags and commands no longer function.
## Bugs Fixed - #709: clarify fleetctl destroy activity - #729: limit amount of work done within a single engine reconciliation attempt - #733: remove
## Bugs Fixed - #726: make etcd timeouts configurable
The signed units feature is deprecated as of this release, primarily because the feature does not fit well with the coming HTTP API. Authentication an…
Both the Engine and the Agent have switched from an event-driven model to a periodic reconciliation model. This was done to ensure fleet is always making progress towards doing the Right Thing™. Unit state is also published at an interval, so stale data in etcd should be much less of a problem.
The signed units feature is deprecated as of this release, primarily because the feature does not fit well with the coming HTTP API. Authentication and authorization are important to get right, and the way the signed units feature is designed just doesn't offer enough security.
TSTATE and DSTATE added to fleetctl list-units, while LOAD and SUB were removed from default field list## Bugs Fixed - #660: fix panic when Job data not found in Registry - #639: lease engine role for extended period of time - #636: remove redundant etc
## Bugs Fixed - #500, #624, #625, #629: switch to reconciler model in engine - #626: fix a race condition in go-systemd
Like the previous release, the majority of effort was spent on the HTTP API (#545) and internal refactoring during this release cycle. While there wer
Like the previous release, the majority of effort was spent on the HTTP API (#545) and internal refactoring during this release cycle. While there weren't any new features released, there were a few notable changes:
fleetctl --verbosity flagLots of effort was spent on the new experimental HTTP API (#545) and internal refactoring this release cycle. While there weren't any new features rel
Lots of effort was spent on the new experimental HTTP API (#545) and internal refactoring this release cycle. While there weren't any new features released, there were two notable changes:
fleetctl debug-info was removed### Features - #303: Richer template unit support - #485: Allow user to choose fields displayed by fleetctl list-machines ### Bugs - #480: fleetctl su
fleetctl list-machinesfleetctl submit no longer fails if units already exist### Features - #235: Add support for mount, auto mount, device unit types - #337: Allow user to choose fields displayed by fleetctl list-units - #179:
fleetctl list-unitsfleetctl list-unitsfleetctl list-machines by IDThis release contains a backport of the fix for #511
This release contains a backport of the fix for #511
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
### Bugs Fixed - #402: Expose more information through user on fleetctl failures - #447: Time out requests to etcd - #450: Call daemon-reload when loa
### Bugs Fixed - #373: check for jobs that have actionable work during engine startup - #407: agent destroys units it should not be running on startup
Nothing published for this version
Nothing published for this version
Improved job state machine - see fleetctl load/unload and the fleetctl list-units STATE column
fleetctl load/unload and the fleetctl list-units STATE columnX-ConditionMachineMetadata unit option (replaces --require flag)X-ConditionMachineID unit option (replaces X-ConditionMachineBootID option).service extension if not provided in fleetctl commandsWhile 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.
One column per quarter.