Merge pull request #890 from weaveworks/v1.2.0-changelog

Expand changelog and update examples and docs, for 1.2.0 release

CHANGELOG.md

@@ -1,3 +1,19 @@
+## 1.2.0 (2018-01-04)
+
+### Improvements
+
+- Releases are more responsive, because dry runs are now done without triggering a sync [weaveworks/flux#862](https://github.com/weaveworks/flux/pull/862)
+- Syncs are much faster, because they are now done all-in-one rather than calling kubectl for each resource [weaveworks/flux#872](https://github.com/weaveworks/flux/pull/872)
+- Rewrite of the image registry package to solve several problems [weaveworks/flux#851](https://github.com/weaveworks/flux/pull/851)
+
+### Fixes
+
+- Support signed manifests (from GCR in particular) [weaveworks/flux#838](https://github.com/weaveworks/flux/issues/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](https://github.com/weaveworks/flux/issues/868)
+- Expand the GCR credentials support to `*.gcr.io` [weaveworks/flux#882](https://github.com/weaveworks/flux/pull/882)
+- Check that the synced git repo is writable before syncing, which avoids a number of indirect failures [weaveworks/flux#865](https://github.com/weaveworks/flux/pull/865)
+- and, [lots of other things](https://github.com/weaveworks/flux/pulls?q=is%3Apr+closed%3A%3E2017-11-01)
+
 ## 1.1.0 (2017-11-01)
 
 ### Improvements

deploy/flux-deployment.yaml

@@ -24,7 +24,7 @@ spec:
         # There are no ":latest" images for flux. Find the most recent
         # release or image version at https://quay.io/weaveworks/flux
         # and replace the tag here.
-        image: quay.io/weaveworks/flux:1.1.0
+        image: quay.io/weaveworks/flux:1.2.0
         imagePullPolicy: IfNotPresent
         ports:
         - containerPort: 3030 # informational

site/daemon.md

@@ -53,13 +53,13 @@ fluxd requires setup and offers customization though a multitude of flags.
 |--git-sync-tag          | `flux-sync`             | tag to use to mark sync progress for this cluster (old config, still used if --git-label is not supplied)|
 |--git-notes-ref         | `flux`            | ref to use for keeping commit annotations in git notes|
 |--git-poll-interval     | `5 minutes`                 | period at which to poll git repo for new commits|
-|**registry**            |                               | |
-|--memcached-hostname    |                               | hostname for memcached service to use when caching chunks; if empty, no memcached will be used|
+|**registry cache**      |                               | (none of these need overriding, usually) |
+|--memcached-hostname    | `memcached` | hostname for memcached service to use for caching image metadata|
 |--memcached-timeout     | `1 second`                   | maximum time to wait before giving up on memcached requests|
 |--memcached-service     | `memcached`                     | SRV service used to discover memcache servers|
-|--registry-cache-expiry | `20 minutes`                  | Duration to keep cached registry tag info. Must be < 1 month.|
+|--registry-cache-expiry | `1 hour`                  | Duration to keep cached registry tag info. Must be < 1 month.|
 |--registry-poll-interval| `5 minutes`                   | period at which to poll registry for new images|
-|--registry-rps          | 200                           | maximum registry requests per second per host|
+|--registry-rps          | `200`                           | maximum registry requests per second per host|
 |--registry-burst        | `125`      | maximum number of warmer connections to remote and memcache|
 |**k8s-secret backed ssh keyring configuration**      |  | |
 |--k8s-secret-name       | `flux-git-deploy`               | name of the k8s secret used to store the private SSH key|

site/using.md

@@ -220,9 +220,9 @@ default:deployment/helloworld  success
 
 # Recording user and message with the triggered action
 
-Issuing a deployment change results in a version control change/git commit, keeping the
-history of the actions. Flux daemon can be started with several flags that impact the commit
-information:
+Issuing a deployment change results in a version control change/git
+commit, keeping the history of the actions. The Flux daemon can be
+started with several flags that impact the commit information:
 
 | flag              | purpose                       | default |
 |-------------------|-------------------------------|------------|
@@ -296,4 +296,3 @@ for b) and c):
 
 git commit: fatal: --author 'unknown' is not 'Name <email>' and matches
 no existing author
-