Flux 1.14.0

This feature release adds a read-only mode to the Flux daemon, adds support for mapping images in HelmRelease resources using YAML dot notation annotations, eases the deployment of Flux with a new fluxctl install command which generates the required YAML manifests, lots of documentation improvements, and many more.

Fixes

• Fetch before branch check to detect upstream changes made after the initial clone fluxcd/flux#2371

Enhancements

• With --git-readonly, fluxd can now sync a git repo without having write access to it. In this mode, fluxd will not make any commits to the repo. fluxcd/flux#1807
• Mapping images in HelmRelease resources using YAML dot notation annotations is now supported fluxcd/flux#2249
• fluxctl has a new install command to ease generating the YAML manifests required to deploy Flux fluxcd/flux#2287
• Kubectl and Kustomize have been upgraded
  • kubectl -> 1.13.8 fluxcd/flux#2327
  • kustomize -> 3.1.0 fluxcd/flux#2299
• The annotation domain has been changed to fluxcd.io, but backwards compatibility with the old (flux.weave.works) domain is maintained fluxcd/flux#2219
• The number of sorts done by ListImagesWithOptions has been reduced fluxcd/flux#2338
• fluxctl will only look for running fluxcd pods while attempting to setup a port forward fluxcd/flux#2283
• --registry-poll-interval has been renamed to --automation-interval to better reflect what it controls; the interval at which automated workloads are checked for updates, and updated. fluxcd/flux#2284
• fluxctl now has a global --timeout flag, which controls how long it waits for jobs sent to fluxd to complete fluxcd/flux#2056

Maintenance and documentation

• Documentation is now hosted on ReadTheDocs fluxcd/flux#2152
• Helm Operator has been removed from the codebase, as it has been moved to a dedicated repository (fluxcd/helm-operator) fluxcd/flux{#2329, #2356}
• Documentation on how to use fluxctl install has been added fluxcd/flux#2298
• Reference about automated image updates has been added to the documentation fluxcd/flux#2369
• Documentation has been added on how to deploy Flux with Kustomize fluxcd/flux#2375
• CLVR, IBM Cloudant, Omise, Replicated, and Yusofleet are now listed as production users (:tada:!) fluxcd/flux{#2331, #2343, #2360, #2373, #2378}
• Various changes to the documentation fluxcd/flux{#2306, #2311, #2313, #2314, #2315, #2332, #2351, #2353, #2358, #2363, #2364, #2365, #2367, #2368, #2372}
• Soon-to-be deprecated version script has been removed from the Snapcraft build configuration fluxcd/flux#2350
• Various typos have been fixed fluxcd/flux{#2348, #2352, #2295}
• Various CI build tweaks (i.a. support preleases containing numbers, Go tarball cleanup after installation, Helm chart release changes) fluxcd/flux{#2301, #2302, #2312, #2320, #2336, #2349, #2361}
• Helm chart repository has been changed to charts.fluxcd.io fluxcd/flux{#2337, #2339, #2341}

Thanks

Many thanks for contributions from @2opremio, @AndriiOmelianenko, @GODBS, @JDavis10213, @MehrCurry, @Sleepy-GH, @adusumillipraveen, @ainmosni, @alanjcastonguay, @aliartiza75, @autarchprinceps, @benmathews, @blancsys, @carlosjgp, @cristian-radu, @Cristian04, @davidkarlsen, @dcherman, @demisx, @derrickburns, @dholbach, @ethan-daocloud, @fred, @gldraphael, @hiddeco, @hlascelles, @ianmiell, @ilya-spv, @jacobsin, @judewin-alef, @jwenz723, @kaspernissen, @knackaron, @ksaritek, @larhauga, @laverya, @linuxbsdfreak, @luxas, @matthewbednarski, @mhumeSF, @mzachh, @nabadger, @obiesmans, @ogerbron, @onedr0p, @paulmil1, @primeroz, @rhockenbury, @runningman84, @rytswd, @semyonslepov, @squaremo, @stealthybox, @stefanprodan, @stefansedich, @suvl, @tjanson, @tomaszkiewicz, @tomcheah, @tschonnie, @ttarczynski, @willholley, @yellowmegaman, @zcourt.

Helm operator 0.10.1

Notice: this release contains a HelmRelease Custom Resource Definition fix. Please make sure you patch the CRD in your cluster.

Bug fixes

• Fixed rollback.timeout definition in the CustomResourceDefinition weaveworks/flux#2251
• Fixed the merge of values weaveworks/flux#2292
• Correct spelling of integrations, and fix make check-generated weaveworks/flux#2312
• Moved successful chart fetch signal to reconcile action (to prevent an infinite loop due to the LastUpdateTime on the condition getting accidentally updated during rollback checks). weaveworks/flux#2316
• Fixed typo in ReasonUpgradeFailed condition change reason weaveworks/flux#2317

Thanks

This release was made possible by contributions from @jfrndz, @adrian, @stefanprodan, @obiesmans, @chriscorn-takt, @sureshamk, @dholbach, @squaremo, and @hiddeco.

Flux 1.13.3

This is a patch release, mostly concerned with adapting documentation to Flux's new home in https://github.com/fluxcd/ and the CNCF sandbox.

Fixes

• Correct the name of the --registry-require argument mentioned in a log message fluxcd/flux#2256
• Parse Docker credentials that have a host and port, but not a scheme fluxcd/flux#2248

Maintenance and documentation

• Change references to weaveworks/flux to fluxcd/flux fluxcd/flux#2240, fluxcd/flux#2244, fluxcd/flux#2257, fluxcd/flux#2271
• Add Walmart to production users (:tada:!) fluxcd/flux#2268
• Mention the multi-tenancy tutorial in the README fluxcd/flux#2286
• Fix the filename given in the .flux.yaml (manifest generation) docs fluxcd/flux#2270
• Run credentials tests in parallel, without sleeping fluxcd/flux#2254
• Correct the Prometheus annotations given in examples fluxcd/flux#2278

Thanks

Thanks to the following for contributions since the last release: @2opremio, @aaron-trout, @adusumillipraveen, @alexhumphreys, @aliartiza75, @ariep, @binjheBenjamin, @bricef, @caniszczyk, @carlosjgp, @carlpett, @chriscorn-takt, @cloudoutloud, @derrickburns, @dholbach, @fnmeissner, @gled4er, @hiddeco, @jmtrusona, @jowparks, @jpellizzari, @ksaritek, @ktsakalozos, @mar1n3r0, @mzachh, @primeroz, @squaremo, @stefanprodan, @sureshamk, @vyckou, @ybaruchel, @zoni.

Flux 1.13.2

This is a patch release, including a fix for problems with using image
labels as timestamps.

Fixes

• Because image labels are inherited from base images, fluxd cannot indiscriminately use labels to determine the image created date. You must now explicitly allow that behaviour with the argument --registry-use-labels weaveworks/flux#2176
• Image timestamps can be missing (or zero) if ordering them by semver version rather than timestamp weaveworks/flux#2175
• Environment variables needed by the Google Cloud SDK helper are now propagated to git weaveworks/flux#2222

Maintenance and documentation

• Image builds are pushed to both weaveworks/ and fluxcd/ orgs on DockerHub, in preparation for the project moving organisations weaveworks/flux#2213
• Calculate Go dependencies more efficiently during the build weaveworks/flux#2207
• Refactor to remove a spurious top-level package weaveworks/flux#2201
• Update the version of Kubernetes-in-Docker used in end-to-end test, to v0.4.0 weaveworks/flux#2202
• Bump the Ubuntu version used in CI weaveworks/flux#2195

Thanks

Thanks go to the following for contributions: @2opremio, @4c74356b41, @ArchiFleKs, @adrian, @alanjcastonguay, @alexanderbuhler, @alexhumphreys, @bobbytables, @derrickburns, @dholbach, @dlespiau, @gaffneyd4, @hiddeco, @hkalsi, @hlascelles, @jaksonwkr, @jblunck, @jwenz723, @linuxbsdfreak, @luxas, @mpashka, @nlamot, @semyonslepov, @squaremo, @stefanprodan, @tegamckinney, @ysaakpr.

Helm operator 0.10.0

This release brings you opt-in automated rollback support, new Prometheus metrics, and experimental support of spawning multiple workers with the --workers=<num> flag to speed up the processing of releases.

This will likely also be the last minor beta release before we promote the Helm operator to its first GA 1.0.0 release.

Notice: the Helm operator relies on changes in the HelmRelease Custom Resource Definition. Please make sure you patch the CRD in your cluster before upgrading the Helm operator.

Bug fixes

• Prevent an infinite release loop when multiple HelmRelease resources with the same release name configuration coexist, by looking at the antecedent annotation set on release resources and confirming ownership weaveworks/flux#2123

Improvements

• Opt-in automated rollback support; when enabled, a failed release will be rolled back automatically and the operator will not attempt a new release until it detects a change in the chart and/or the configured values weaveworks/flux#2006

• Increase timeout for annotating resources from a Helm release, to cope with large umbrella charts weaveworks/flux#2123

• New Prometheus metrics

  • release_queue_length_count
  • release_duration_seconds{action=['INSTALL','UPGRADE'], dry-run=['true', 'false'], success=['true','false'], namespace, releasename}

  weaveworks/flux#2191

• Experimental support of spawning multiple queue workers processing releases by configuring the --workers=<num> flag weaveworks/flux#2194

Maintenance and documentation

• Publish images to fluxcd DockerHub organization weaveworks/flux#2213
• Document opt-in rollback feature weaveworks/flux#2220

Thanks

Many thanks to @adrian, @2opremio, @semyonslepov, @gtseres, @squaremo, @stefanprodan, @kingdonb, @ncabatoff, @dholbach, @cristian-radu, @simonmacklin, @hiddeco for contributing to this release.

Flux 1.13.1

This is a patch release.

Fixes

• Use a context with a timeout for every request that comes through the upstream connection, so they may be abandoned if taking too long weaveworks/flux#2171
• Initialise the high-water mark once, so it doesn't get continually reset and cause notification noise weaveworks/flux#2177
• Force tag updates when making local clones, to account for changes in git 2.20 weaveworks/flux#2184

Thanks

Cheers to the following people for their contributions: @2opremio, @J-Lou, @aarnaud, @adrian, @airmap-madison, @alanjcastonguay, @arsiesys, @atbe-crowe, @azazel75, @bia, @carlosjgp, @chriscorn-takt, @cristian-radu, @davidkarlsen, @derrickburns, @dholbach, @dlespiau, @errordeveloper, @ewoutp, @hiddeco, @humayunjamal, @isen-ng, @judewin-alef, @kevinm444, @muhlba91, @roaddemon, @runningman84, @squaremo, @starkers, @stefanprodan, @sukrit007, @willholley.

Flux 1.13.0

This feature release contains an experimental feature for generating manifests from the sources in git and completes the support for GPG signatures.

Fixes

• Use openssh-client rather than openssh in container image weaveworks/flux#2142
• Cope when filenames from git start or end with spaces weaveworks/flux#2117
• Ignore metrics API group, known to be problematic weaveworks/flux#2096
• Remove a possible deadlock from code calling git weaveworks/flux#2086

Enhancements

• When --manifest-generation is set, look for .flux.yaml files in the git repo and generate manifests according to the instructions therein (see the docs) weaveworks/flux#1848
• Verify GPG signatures on commits (when --git-verify-signatures is set; see the docs) weaveworks/flux#1791
• Make the log format configurable (specifically to admit JSON logging) weaveworks/flux#2138
• Log when a requested workload is not of a kind known to fluxd weaveworks/flux#2097
• Get image build time from OCI labels, if present weaveworks/flux#1992, weaveworks/flux#2084
• A new flag --garbage-collection-dry-run will report what would be deleted by garbage collection in the log, without deleting it weaveworks/flux#2063

Maintenance and documentation

• Let fluxd be run outside a cluster, for development convenience weaveworks/flux#2140
• Documentation edits weaveworks/flux#2134, weaveworks/flux#2109
• Improve some tests weaveworks/flux#2111, weaveworks/flux#2110, weaveworks/flux#2085, weaveworks/flux#2090
• Give the memcached pod a security context weaveworks/flux#2125
• Move to go modules and abandon go dep weaveworks/flux#2083, weaveworks/flux#2127, weaveworks/flux#2094
• Give an example of DNS settings in the example deployment weaveworks/flux#2116
• Document how to get the fluxctl snap weaveworks/flux#1966, weaveworks/flux#2108
• Give more guidance on how to contribute to Flux weaveworks/flux#2104
• Speed CI builds up by using CircleCI caching weaveworks/flux#2078

Thanks

Many thanks for contributions from @2opremio, @AndriiOmelianenko, @ArchiFleKs, @RGPosadas, @RoryShively, @alanjcastonguay, @amstee, @arturo-c, @azazel75, @billimek, @brezerk, @bzon, @derrickburns, @dholbach, @dminca, @dmitri-lerko, @guzmo, @hiddeco, @imrtfm, @jan-schumacher, @jp83, @jpds, @kennethredler, @leoblanc, @marcelonaso, @marcossv9, @marklcg, @michaelgeorgeattard, @mrkaran, @nabadger, @ncabatoff, @primeroz, @rdubya16, @rjanovski, @rkouyoumjian, @rndstr, @runningman84, @squaremo, @stefanprodan, @stefansedich, @suvl, @tckb, @timja, @vovkanaz, @willholley.

Helm operator 0.9.2

Bug fixes

• Ensure releases are enqueued on clone change only weaveworks/flux#2081
• Reorder start of processes on boot and verify informer cache sync early, to prevent the operator from hanging on boot weaveworks/flux#2103
• Use openssh-client rather than openssh in container image weaveworks/flux#2142

Improvements

• Enable pprof to ease profiling weaveworks/flux#2095

Maintenance and documentation

• Add notes about production setup Tiller weaveworks/flux#2146

Thanks

Thanks @2opremio, @willholley, @runningman84, @stefanprodan, @squaremo, @rossf7, @hiddeco for contributing.

Flux 1.12.3

This is a patch release.

Fixes

• Show tag image for workload in list-images
  weaveworks/flux#2024
• Log warning when not applying resource by namespace
  weaveworks/flux#2034
• Always list the status of a workload in fluxctl
  weaveworks/flux#2035
• Ensure Flux installs gnutls >=3.6.7, to resolve security scan issues
  weaveworks/flux#2044
• Rename controller to workload in fluxctl release
  weaveworks/flux#2048
• Give full output of git command on errors
  weaveworks/flux#2054

Maintenance and documentation

• Warn about Flux only supporting YAML and not JSON
  weaveworks/flux#2010
• Fix and refactor end-to-end tests
  weaveworks/flux#2050 weaveworks/flux#2058

Thanks

Thanks to @2opremio, @hiddeco, @squaremo and @xtellurian for contributions.

Helm operator 0.9.1

Bug fixes

• During the lookup of HelmReleases for a mirror, ensure the resource has a git chart source before comparing the mirror name weaveworks/flux#2027

Thanks

Thanks to @puzza007, @squaremo, @2opremio, @stefanprodan, @hiddeco for reporting the issue, patching and reviewing it.