more Flux → Weave Flux

Daniel Holbach · hiddeco · commit 198a961b29ee · 2019-06-25T14:39:08.000+02:00
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -1,6 +1,6 @@
 ---
 name: Bug report
-about: Create a report to help us improve Weave Flux
+about: Create a report to help us improve Flux
 title: ''
 labels: blocked-needs-validation, bug
 assignees: ''
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,6 +1,6 @@
 ---
 name: Feature request
-about: Suggest a new feature for Weave Flux
+about: Suggest a new feature for Flux
 title: ''
 labels: blocked-needs-validation, enhancement
 assignees: ''
diff --git a/README.md b/README.md
@@ -142,7 +142,7 @@ be interested in the following:
 
 If you have any questions about Flux and continuous delivery:
 
-- Read [the Weave Flux docs](https://github.com/weaveworks/flux/tree/master/site).
+- Read [the Flux docs](https://github.com/weaveworks/flux/tree/master/site).
 - Invite yourself to the <a href="https://slack.weave.works/" target="_blank">Weave community</a>
   slack and ask a question on the [#flux](https://weave-community.slack.com/messages/flux/)
   channel.
diff --git a/chart/flux/README.md b/chart/flux/README.md
@@ -179,7 +179,7 @@ You should also remove the deploy key from your GitHub repository.
 
 ### Configuration
 
-The following tables lists the configurable parameters of the Weave Flux chart and their default values.
+The following tables lists the configurable parameters of the Flux chart and their default values.
 
 | Parameter                                         | Default                                              | Description
 | -----------------------------------------------   | ---------------------------------------------------- | ---
@@ -299,7 +299,7 @@ weaveworks/flux
 
 ### Upgrade
 
-Update Weave Flux version with:
+Update Flux version with:
 
 ```sh
 helm upgrade --reuse-values flux \
diff --git a/site/annotations-tutorial.md b/site/annotations-tutorial.md
@@ -1,6 +1,6 @@
-# Driving Weave Flux - automations, locks and annotations
+# Driving Flux - automations, locks and annotations
 
-In this tutorial we want to get a better feel for what we can do with Weave
+In this tutorial we want to get a better feel for what we can do with 
 Flux. We won't spend too much time with getting it up and running, so let's
 get that out of the way first.
 
@@ -11,7 +11,7 @@ deployment](https://github.com/weaveworks/flux-get-started) and click on the
 
 ## Setup
 
-Get the source code of Weave Flux:
+Get the source code of Flux:
 
 ```sh
 git clone https://github.com/weaveworks/flux
@@ -83,7 +83,7 @@ Apply the Helm Release CRD:
 kubectl apply -f https://raw.githubusercontent.com/weaveworks/flux/master/deploy-helm/flux-helm-release-crd.yaml
 ```
 
-Install Weave Flux and its Helm Operator by specifying your fork URL. Just
+Install Flux and its Helm Operator by specifying your fork URL. Just
 make sure you replace `YOURUSER` with your GitHub username in the command
 below:
 
@@ -108,14 +108,14 @@ running `kubectl get pods --all-namespaces`).
 
 In the second step we will use fluxctl to talk to Flux in the cluster and
 interact with the deployments. First, please [install fluxctl](fluxctl.md#installing-fluxctl).
-(It enables you to drive all of Weave Flux, so have a look at the output of
+(It enables you to drive all of Flux, so have a look at the output of
 `fluxctl -h` to get a better idea.)
 
 > **Note:** Another option (without installing `fluxctl` is to take a look
 at the resulting annotation changes and make the changes in Git. This is
 GitOps after all. :-)
 
-To enable Weave Flux to sync your config, you need to add the deployment key
+To enable Flux to sync your config, you need to add the deployment key
 to your fork.
 
 Get your Flux deployment key by running
@@ -134,11 +134,11 @@ Wait for sync to happen or run
 fluxctl sync
 ```
 
-## Driving Weave Flux
+## Driving Flux
 
-After syncing, Weave Flux will find out which workloads there are, which
+After syncing, Flux will find out which workloads there are, which
 images are available and what needs doing. To find out which workloads are
-managed by Weave Flux, run
+managed by Flux, run
 
 ```sh
 fluxctl list-workloads -a
@@ -167,7 +167,7 @@ Commit pushed:  4755a3b
 ```
 
 If you now go back to `https://github.com/YOUR-USER-ID/flux-get-started` in
-your browser, you will notice that Weave Flux has made a commit on your
+your browser, you will notice that Flux has made a commit on your
 behalf. The policy change is now in Git, which is great for transparency and
 for defining expected state.
 
@@ -265,7 +265,7 @@ and the diff for this is going to look like this:
 ```
 
 And that's it. At the end of this tutorial, you have automated, locked and
-annotated deployments with Weave Flux.
+annotated deployments with Flux.
 
 Another tip, if you should get stuck anywhere: check what Flux is doing. You
 can do that by simply running
diff --git a/site/building.md b/site/building.md
@@ -1,5 +1,5 @@
 ---
-title: Building Weave Flux
+title: Building Flux
 menu_order: 80
 ---
 
diff --git a/site/faq.md b/site/faq.md
@@ -1,5 +1,5 @@
 ---
-title: Weave Flux FAQ
+title: Flux FAQ
 menu_order: 60
 ---
 
diff --git a/site/fluxctl.md b/site/fluxctl.md
@@ -1,5 +1,5 @@
 ---
-title: Using Weave Flux
+title: Using Flux
 menu_order: 40
 ---
 
diff --git a/site/get-started.md b/site/get-started.md
@@ -1,5 +1,5 @@
 ---
-title: Installing Weave Flux Manually
+title: Installing Flux Manually
 menu_order: 10
 ---
 
@@ -152,4 +152,4 @@ As a next step, you might want to dive deeper into [how to
 control Flux](./fluxctl.md), check out [more sophisticated
 setups](./standalone-setup.md) or go through our hands-on
 tutorial about driving Flux, e.g.
-[automations, annotations and locks](annotations-tutorial.md).
+[automations, annotations and locks](annotations-tutorial.md).
diff --git a/site/helm-get-started.md b/site/helm-get-started.md
@@ -1,11 +1,11 @@
 ---
-title: Installing Weave Flux using Helm
+title: Installing Flux using Helm
 menu_order: 20
 ---
 
 - [Get started with Flux using Helm](#get-started-with-flux-using-helm)
   * [Prerequisites](#prerequisites)
-  * [Install Weave Flux](#install-weave-flux)
+  * [Install Flux](#install-flux)
   * [Giving write access](#giving-write-access)
   * [Committing a small change](#committing-a-small-change)
   * [Conclusion](#conclusion)
@@ -60,7 +60,7 @@ helm init --skip-refresh --upgrade --service-account tiller --history-max 10
 > and be aware of the `--history-max` flag before promoting to
 > production.
 
-## Install Weave Flux
+## Install Flux
 
 Add the Flux repository of Weaveworks:
 
@@ -74,12 +74,12 @@ Apply the Helm Release CRD:
 kubectl apply -f https://raw.githubusercontent.com/weaveworks/flux/master/deploy-helm/flux-helm-release-crd.yaml
 ```
 
-In this next step you install Weave Flux using `helm`. Simply
+In this next step you install Flux using `helm`. Simply
 
  1. Fork [flux-get-started](https://github.com/weaveworks/flux-get-started)
     on GitHub and replace the `weaveworks` with your GitHub username in
     [here](https://github.com/weaveworks/flux-get-started/blob/master/releases/ghost.yaml#L13)
- 1. Install Weave Flux and its Helm Operator by specifying your fork URL:
+ 1. Install Flux and its Helm Operator by specifying your fork URL:
 
       *Just make sure you replace `YOURUSER` with your GitHub username
       in the command below:*
@@ -203,4 +203,4 @@ Flux](fluxctl.md) or go through our hands-on tutorial about driving Flux,
 e.g. [automations, annotations and locks](annotations-tutorial.md).
 
 For a more advanced Helm setup, take a look at the [gitops-helm
-repository](https://github.com/stefanprodan/gitops-helm).
+repository](https://github.com/stefanprodan/gitops-helm).
diff --git a/site/helm-operator.md b/site/helm-operator.md
@@ -30,11 +30,11 @@ helm-operator requires setup and offers customization though a multitude of flag
 | --log-release-diffs       | `false`                       | Log the diff when a chart release diverges. **Potentially insecure.**
 | --update-chart-deps       | `true`                        | Update chart dependencies before installing or upgrading a release.
 
-## Installing Weave Flux Helm Operator and Helm with TLS enabled
+## Installing Flux Helm Operator and Helm with TLS enabled
 
 ### Installing Helm / Tiller
 
-Generate certificates for Tiller and Flux. This will provide a CA, servercerts for Tiller and client certs for Helm / Weave Flux.
+Generate certificates for Tiller and Flux. This will provide a CA, servercerts for Tiller and client certs for Helm / Flux.
 
 > **Note:** When creating the certificate for Tiller the Common Name should match the hostname you are connecting to from the Helm operator.
 
@@ -171,7 +171,7 @@ helm --tls --tls-verify \
   ls
 ```
 
-### Deploy Weave Flux Helm Operator
+### Deploy Flux Helm Operator
 
 First create a new Kubernetes TLS secret for the client certs;
 
diff --git a/site/how-it-works.md b/site/how-it-works.md
@@ -1,5 +1,5 @@
 ---
-title: How Weave Flux Works
+title: How Flux Works
 menu_order: 20
 ---
 
diff --git a/site/installing.md b/site/installing.md
@@ -1,5 +1,5 @@
 ---
-title: Installing Weave Flux
+title: Installing Flux
 menu_order: 30
 ---
 
@@ -10,7 +10,7 @@ contains [manifests][k8s-manifests] (as YAML files) describing what
 should run in the cluster. Flux imposes
 [some requirements](/site/requirements.md) on these files.
 
-# Installing Weave Flux
+# Installing Flux
 
 Here are the instructions to [install Flux on your own
 cluster](./get-started.md).
diff --git a/site/introduction.md b/site/introduction.md
@@ -1,5 +1,5 @@
 ---
-title: Introducing Weave Flux
+title: Introducing Flux
 menu_order: 10
 ---
 
diff --git a/site/monitoring.md b/site/monitoring.md
@@ -1,5 +1,5 @@
 ---
-title: Monitoring Weave Flux
+title: Monitoring Flux
 menu_order: 70
 ---
 
diff --git a/site/troubleshooting.md b/site/troubleshooting.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting Weave Flux
+title: Troubleshooting Flux
 menu_order: 50
 ---
 
diff --git a/snap/snapcraft.yaml b/snap/snapcraft.yaml
@@ -9,9 +9,9 @@ version-script: |
     echo "$FLUX_TAG+$GIT_REV"
   fi
 version: git
-summary: fluxctl talks to Weave Flux and helps you deploy your code
+summary: fluxctl talks to Flux and helps you deploy your code
 description: |
-  fluxctl talks to your Weave Flux instance and exposes all its
+  fluxctl talks to your Flux instance and exposes all its
   functionality to an easy to use command line interface.
 grade: devel # must be 'stable' to release into candidate/stable channels
 confinement: strict
