Flux 1.2.0 release

Improvements

• Releases are more responsive, because dry runs are now done without triggering a sync weaveworks/flux#862
• Syncs are much faster, because they are now done all-in-one rather than calling kubectl for each resource weaveworks/flux#872
• Rewrite of the image registry package to solve several problems weaveworks/flux#851

Fixes

• Support signed manifests (from GCR in particular) weaveworks/flux#838
• Support CronJobs from Kubernetes API version batch/v1beta1, which are present in Kubernetes 1.7 (while those from batch/b2alpha1 are not) weaveworks/flux#868
• Expand the GCR credentials support to *.gcr.io weaveworks/flux#882
• Check that the synced git repo is writable before syncing, which avoids a number of indirect failures weaveworks/flux#865
• and, lots of other things

Flux 1.1.0 Release

Improvements

• Flux can now release updates to DaemonSets, StatefulSets and CronJobs in addition to Deployments.
• Matching Service resources are no longer required.

Breaking Changes

As a consequence of these improvements, we have had to retire the ability to release updates to Deployment resources by specifying the name of a matching Service. In practical terms this means that you will use list-controllers instead of list-services, and refer to controllers directly using the --controller argument instead of indirectly via --service:

• fluxctl list-services is no longer supported; use fluxctl list-controllers instead
• fluxctl commands which used to accept a --service=<namespace>/<servicename> parameter now accept --controller=<namespace>:<kind>/<name> instead, where <kind> is one of deployment, daemonset, statefulset or cronjob
• Tabular outputs from fluxctl that used to mention SERVICE now mention CONTROLLER instead. The format of controller identifiers matches that of the new --controller argument.

Flux 1.0.2 Release

Improvements

• Implemented support for v2 registry manifests.

Flux 1.0.1 Release

Improvements

• Flux daemon can be configured to populate the git commit author with the name of the requesting user
• When multiple flux daemons share the same configuration repository, each fluxd only sends Slack notifications for commits that affect its branch/path
• When a resource is locked the invoking user is recorded, along with an optional message
• When a new config repo is synced for the first time, don't send notifications for the entire commit history

Fixes

• The fluxctl identity command only worked via the Weave Cloud service, and not when connecting directly to the daemon

Flux 1.0.0 Release

Warning This release has significant changes over prior releases, and is not in general backwards-compatible:

• The image name for the daemon has changed to quay.io/weaveworks/flux. There is no longer a need to run the service (and at some point, the code for fluxsvc will be moved elsewhere).
• The command-line tool fluxctl will no longer work with old installations (however, for some purposes, old binaries of fluxctl will work with Weave Cloud).

Changes

• The purpose of Flux is now to synchronise your cluster with config stored in git.
• ... and to automatically upgrade images when new versions are ready to deploy.
• This is all done in the daemon running in your cluster; no secrets need to live anywhere else or leave your cluster.
• Automated image upgrades are controlled by annotations on the resources in question.
• Automated image upgrades are no longer limited to releasing just the latest pushed tag. Run fluxctl policy --help to learn more.

Upgrading

To upgrade from a prior version of Flux, delete the Kubernetes resources associated with the old version, then adapt the example yamels by supplying at least a URL for your config repository. Be sure to set up an SSH key, as described in the setup docs.

If you want to connect to Weave Cloud, supply your instance token and the --connect argument where indicated in the example yamel. Weave Cloud will detect the version of the daemon you are using and show you the right UI.

Version 0.3.0 Update Kubernetes support to 1.6.1

Potentially breaking changes

• Support for Kubernetes' ReplicationControllers is deprecated; please
  update these to Deployments, which do the same job but much better
  (see
  https://kubernetes.io/docs/user-guide/replication-controller/#deployment-recommended)
• The service<->daemon protocol is versioned. The daemon will now
  crash-loop, printing a warning to the log, if it tries to connect to
  the service with a deprecated version of the protocol.

Improvements

• Updated the version of kubectl bundled in the Flux daemon image,
  to work with newer (>1.5) Kubernetes.
• Added fluxctl save command for bootstrapping a repo from an existing cluster
• You can now record a message and username with each release, which
  show up in notifications

v0.2.0

More helpful.

Features

• Lots more documentation
• More informative output from fluxctl release
• Added option in fluxctl set-config to generate a deploy key

Improvements

• Slack notifications are tidier
• Support for releasing to >1 service at a time
• Better behaviour when flux deploys itself
• More help given for commonly encountered errors
• Filter out Kubernetes add-ons from consideration
• More consistent Prometheus metric labeling

All issues closed with this release

0.1.0

See the changelog

master-0d109dd (supports v4 release API)

• Supports v4 release endpoints

master-ccb9a99 (ad-hoc release)

Tag ad-hoc release