The promise of continuous delivery relies upon automation and in recent years the automation of building and testing software has become commonplace. But it is comparatively difficult to automate the deployment and monitoring of an application. Weave Cloud fixes this problem.

Weave Cloud is a SaaS product by Weaveworks that brings you the best of Flux, as well as:

  • a UI and alerts for deployments: nicely integrated overview, all Flux operations just a click away.
  • full observability and insights into your cluster: Instantly start using monitoring dashboards for your cluster, hosted 13 months of history, use a realtime map of your cluster to debug and analyse its state.

Installing Flux Helm Operator for Weave Cloud

In order to use the Helm operator with Weave Cloud you have to apply the HelmRelease CRD definition and the operator deployment in the weave namespace:

export REPO=

kubectl apply -f ${REPO}/deploy-helm/flux-helm-release-crd.yaml
kubectl apply -f ${REPO}/deploy-helm/weave-cloud-helm-operator-deployment.yaml

Check the operator logs with:

kubectl -n weave logs deployment/flux-helm-operator -f

Note: The above instructions are assuming that Tiller is deployed in the kube-system namespace without TLS.

“The request failed authentication”

If you integrated your pre-existing Flux with Weave Cloud and you are seeing the error message The request failed authentication, this probably means you haven’t supplied the token. You can get the token from the settings in Weave Cloud; set the environment variable FLUX_SERVICE_TOKEN to the token and FLUX_URL= as well.

If you have set Flux up standalone (as in the instructions in its Get Started docs), this probably means Flux is defaulting to using Weave Cloud because you’ve not set the environment variable FLUX_URL to point at the daemon. See the docs.