All Versions
77
Latest Version
Avg Release Cycle
42 days
Latest Release
207 days ago
Changelog History
Page 7
Changelog History
Page 7
-
v1.2.0 Changes
January 04, 2018๐ 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 frombatch/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
-
v1.1.0 Changes
November 01, 2017๐ Improvements
- ๐ Flux can now release updates to DaemonSets, StatefulSets and CronJobs in addition to Deployments. Matching Service resources are no longer required.
-
v1.0.2 Changes
October 18, 2017๐ Improvements
- ๐ Implemented support for v2 registry manifests.
-
v1.0.1 Changes
September 19, 2017๐ 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
-
v1.0.0 Changes
August 22, 2017๐ This release introduces significant changes to the way Flux works:
- The git repository is now the system of record for your cluster state. Flux continually works to synchronise your cluster with the config repository
- ๐ Release, automation and policy actions work by updating the config repository
๐ See https://github.com/weaveworks/flux/releases/tag/1.0.0 for full details.
-
v0.16.0
November 28, 2019 -
v0.15.0
October 07, 2019 -
v0.14.1
September 04, 2019 -
v0.14.0
August 22, 2019 -
v0.13.0
August 21, 2019