weave.works.flux annotations -> fluxcd.io

Author: hiddeco

docs/faq.md

@@ -309,7 +309,7 @@ Yes. The easiest way to do that is to use the following annotation
 *in the manifest files*:
 
 ```yaml
-    flux.weave.works/ignore: true
+    fluxcd.io/ignore: true
 ```
 
 To stop ignoring these annotated resources, you simply remove the
@@ -329,7 +329,7 @@ If the annotation is just carried in the cluster, the easiest way
 to remove it is to run:
 
 ```sh
-kubectl annotate <resource> "flux.weave.works/ignore"-
+kubectl annotate <resource> "fluxcd.io/ignore"-
 ```
 
 Mixing both kinds of annotations (in-git and in-cluster), can make

docs/references/fluxctl.md

@@ -302,7 +302,7 @@ default:deployment/helloworld  helloworld  quay.io/weaveworks/helloworld:master-
 ```
 
 Automation can also be enabled by adding the annotation
-`flux.weave.works/automated: "true"` to the deployment.
+`fluxcd.io/automated: "true"` to the deployment.
 
 We can see that the `list-workloads` subcommand reports that the
 helloworld application is automated. Flux will now automatically
@@ -600,9 +600,9 @@ no existing author
 Automation and image tag filtering can also be managed using annotations
 (`fluxctl` is using the same mechanism).
 
-Automation can be enabled with `flux.weave.works/automated: "true"`. Image
+Automation can be enabled with `fluxcd.io/automated: "true"`. Image
 filtering annotations take the form
-`flux.weave.works/tag.<container-name>: <filter-type>:<filter-value>` or 
+`fluxcd.io/tag.<container-name>: <filter-type>:<filter-value>` or 
 `filter.fluxcd.io/<container-name>: <filter-type>:<filter-value>`. Values of
 `filter-type` can be [`glob`](#glob), [`semver`](#semver), and
 [`regexp`](#regexp). Filter values use the same syntax as when the filter is
@@ -619,8 +619,8 @@ metadata:
   labels:
     app: podinfo
   annotations:
-    flux.weave.works/automated: "true"
-    flux.weave.works/tag.podinfod: semver:~1.3
+    fluxcd.io/automated: "true"
+    fluxcd.io/tag.podinfod: semver:~1.3
 spec:
   selector:
     matchLabels:
@@ -644,8 +644,8 @@ spec:
 Things to notice:
 
 1. The annotations are made in `metadata.annotations`, not in `spec.template.metadata`.
-2. The `flux.weave.works/tag.`... references the container name `podinfod`, this will change based on your container name. If you have multiple containers you would have multiple lines like that.
-3. The value for the `flux.weave.works/tag.`... annotation should includes the filter pattern type, in this case `semver`.
+2. The `fluxcd.io/tag.`... references the container name `podinfod`, this will change based on your container name. If you have multiple containers you would have multiple lines like that.
+3. The value for the `fluxcd.io/tag.`... annotation should includes the filter pattern type, in this case `semver`.
 
 Annotations can also be used to tell Flux to temporarily ignore certain manifests
-using `flux.weave.works/ignore: "true"`. Read more about this in the [FAQ](../faq.md).
+using `fluxcd.io/ignore: "true"`. Read more about this in the [FAQ](../faq.md).

docs/references/fluxyaml-config-files.md

@@ -101,7 +101,7 @@ commandUpdated:
       policy:
         command: >-
           cat flux-patch.yaml |
-          kubeyaml annotate --namespace $FLUX_WL_NS --kind $FLUX_WL_KIND --name $FLUX_WL_NAME "flux.weave.works/$FLUX_POLICY=$FLUX_POLICY_VALUE"
+          kubeyaml annotate --namespace $FLUX_WL_NS --kind $FLUX_WL_KIND --name $FLUX_WL_NAME "fluxcd.io/$FLUX_POLICY=$FLUX_POLICY_VALUE"
           > new-flux-patch.yaml &&
           mv new-flux-patch.yaml flux-patch.yaml
 ```
@@ -164,7 +164,7 @@ In addition, `updaters` are provided with some environment variables:
   * `FLUX_IMG`: Image name which the container needs to be updated to (e.g. `nginx`).
   * `FLUX_TAG`: Image tag which the container needs to be updated to (e.g. `1.15`).
 * `policy` updaters are provided with:
-  * `FLUX_POLICY`: the name of the policy to be added or updated in the workload. To make into an annotation name, prefix with `flux.weave.works/`
+  * `FLUX_POLICY`: the name of the policy to be added or updated in the workload. To make into an annotation name, prefix with `fluxcd.io/`
   * `FLUX_POLICY_VALUE`: value of the policy to be added or updated in the controller. If the `FLUX_POLICY_VALUE`
   environment variable is not set, it means the policy should be removed.
 

docs/references/helm-operator-integration.md

@@ -141,8 +141,8 @@ Top level image example:
 kind: HelmRelease
 metadata:
   annotations:
-    flux.weave.works/automated: "true"
-    flux.weave.works/tag.chart-image: semver:~4.0
+    fluxcd.io/automated: "true"
+    fluxcd.io/tag.chart-image: semver:~4.0
 spec:
   values:
     image:
@@ -156,9 +156,9 @@ Sub-section images example:
 kind: HelmRelease
 metadata:
   annotations:
-    flux.weave.works/automated: "true"
-    flux.weave.works/tag.prometheus: semver:~2.3
-    flux.weave.works/tag.alertmanager: glob:v0.15.*
+    fluxcd.io/automated: "true"
+    fluxcd.io/tag.prometheus: semver:~2.3
+    fluxcd.io/tag.alertmanager: glob:v0.15.*
     filter.fluxcd.io/nats: regex:^0.6.*
 spec:
   values:

docs/tutorials/driving-flux.md

@@ -179,11 +179,11 @@ It should look a little something like this:
 @@ -8,8 +8,8 @@ metadata:
      app: podinfo
    annotations:
-     flux.weave.works/automated: "true"
--    flux.weave.works/tag.init: regexp:^3.*
--    flux.weave.works/tag.podinfod: semver:~1.3
-+    flux.weave.works/tag.init: glob:1.4.*
-+    flux.weave.works/tag.podinfod: glob:1.4.*
+     fluxcd.io/automated: "true"
+-    fluxcd.io/tag.init: regexp:^3.*
+-    fluxcd.io/tag.podinfod: semver:~1.3
++    fluxcd.io/tag.init: glob:1.4.*
++    fluxcd.io/tag.podinfod: glob:1.4.*
  spec:
    strategy:
      rollingUpdate:
@@ -223,10 +223,10 @@ The resulting diff should look like this
 @@ -10,6 +10,7 @@ metadata:
      app: podinfo
    annotations:
-     flux.weave.works/automated: "true"
-     flux.weave.works/tag.init: glob:1.4.*
-     flux.weave.works/tag.podinfod: glob:1.4.*
-+    flux.weave.works/locked: 'true'
+     fluxcd.io/automated: "true"
+     fluxcd.io/tag.init: glob:1.4.*
+     fluxcd.io/tag.podinfod: glob:1.4.*
++    fluxcd.io/locked: 'true'
  spec:
    strategy:
      rollingUpdate:
@@ -275,5 +275,5 @@ kubectl logs -n default deploy/flux -f
 ```
 
 If you should have any questions, find us on Slack in the [#flux
-channel](https://weave-community.slack.com/messages/flux/), get
-an invite to it [here](https://slack.weave.works/).
+channel](https://cncf.slack.com/messages/flux/), get
+an invite to it [here](https://slack.cncf.io).