Implement automation via kyaml setters2

README.md

@@ -32,31 +32,34 @@ the GitRepository kind, and doesn't need the source-controller itself.
 If you're not already using the [GitOps toolkit][gotk], you can just
 install the custom resource definition for GitRepository:
 
-    kubectl apply -f https://raw.githubusercontent.com/fluxcd/source-controller/master/config/crd/bases/source.toolkit.fluxcd.io_gitrepositories.yaml
+    kubectl apply -f https://raw.githubusercontent.com/fluxcd/source-controller/v0.0.18/config/crd/bases/source.toolkit.fluxcd.io_gitrepositories.yaml
 
 **To install the image reflector controller**
 
 This controller relies on the image reflector controller. A working
 configuration for the latter can be applied straight from the GitHub
-repository (NB `-k`):
+repository:
 
-    kubectl apply -k github.com/fluxcd/image-reflector-controller/config/default
+    kustomize build github.com/fluxcd/image-reflector-controller//config/default/?ref=main | kubectl apply -f-
 
 ### Installing the automation controller
 
 You can apply a working configuration directly from GitHub:
 
-    kubectl apply -k github.com/fluxcd/image-automation-controller/config/default
+    kustomize build github.com/fluxcd/image-automation-controller//config/default?ref=main | kubectl apply -f-
 
 or, in a clone of this repository,
 
     make docker-build deploy
 
+You will need to do the latter if you're trying the controller on a
+branch other than `main`.
+
 ## How to use it
 
 Here is a quick example of configuring an automation. I'm going to use
-[cuttlefacts-app][cuttlefacts-app-repo] because it's minimal and
-thereby, easy to follow.
+[cuttlefacts-app][cuttlefacts-app-repo] because it's minimal and easy
+to follow.
 
 ### Image policy
 
@@ -92,7 +95,7 @@ kind: ImagePolicy
 metadata:
   name: app-policy
 spec:
-  imageRepository:
+  imageRepositoryRef:
     name: app-image
   policy:
     semver:
@@ -111,7 +114,7 @@ NAME         LATESTIMAGE
 app-policy   cuttlefacts/cuttlefacts-app:1.0.0
 ```
 
-### Git repository and automation
+### Creating the git repository object
 
 You need a writable git repository, so fork
 [`cuttlefacts-app`][cuttlefacts-app-repo] to your own account, and
@@ -176,9 +179,9 @@ EOF
 $ $EDITOR repo.yaml
 ```
 
-Create the repository; be aware that unless you're running the full
-GitOps toolkit suite, there will be no controller acting on it (and
-doesn't need to be, for the purpose of this run-through).
+Create the repository object; be aware that unless you're running the
+full GitOps toolkit suite, there will be no controller acting on it
+(and doesn't need to be, for the purpose of this run-through).
 
 ```bash
 $ kubectl apply -f repo.yaml
@@ -188,9 +191,50 @@ NAME               URL                                             READY   STATU
 cuttlefacts-repo   ssh://git@github.com/squaremo/cuttlefacts-app                    9s
 ```
 
+### Adding a marker to the YAML to update
+
+To tell the controller what to update, you add some markers to the
+files to be updated. Each marker says which field to update, and which
+image policy to use for the new value.
+
+In this case, it's the image in the deployment that needs to be
+updated, with the latest image from the image policy made
+earlier. Edit the file either locally or through GitHub, and add a
+marker to the file `deploy/deployment.yaml` at the line with the image
+field, `image: cuttlefacts/cuttlefacts-app`. The surrounding lines
+look like this:
+
+```
+      containers:
+      - name: server
+        image: cuttlefacts/cuttlefacts-app
+        imagePullPolicy: IfNotPresent
+```
+
+With the marker, they look like this:
+
+```
+      containers:
+      - name: server
+        image: cuttlefacts/cuttlefacts-app # {"$imagepolicy": "default:app-policy"}
+        imagePullPolicy: IfNotPresent
+```
+
+The marker is a comment at the end of the `image:` line, with a JSON
+value (so remember the double quotes), naming the image policy object
+to use for the value. A `:` character separates the namespace from the
+name of the `ImagePolicy` object. (The namespace is default because it
+wasn't specified in the manifest (`policy.yaml`) or when it was
+applied.)
+
+Commit that change, and push it if you made the commit locally.
+
+### Creating the automation object
+
 Now we have an image policy, which calculates the most recent image,
-and a git repository to update -- the last ingredient is to tie them
-together with an `ImageUpdateAutomation` resource:
+and a git repository to update, and we've marked the field to update,
+in a file. The last ingredient is to tie these together with an
+`ImageUpdateAutomation` resource:
 
 ```
 $ cat > update.yaml <<EOF
@@ -199,19 +243,23 @@ kind: ImageUpdateAutomation
 metadata:
   name: update-app
 spec:
-  gitRepository:
-    name: cuttlefacts-repo
+  checkout:
+    gitRepositoryRef:
+      name: cuttlefacts-repo
   update:
-    imagePolicy:
-      name: app-policy
+    setters:
+      paths:
+      - .
   commit:
     authorName: UpdateBot
     authorEmail: bot@example.com
 EOF
 ```
 
-Note that the image policy you created earlier, and the git
-repository, are both mentioned.
+The git repository object is mentioned, and the `setters` value gives
+the paths to apply updates under.
+
+Apply the file to create the automation object:
 
     kubectl apply -f update.yaml
 
@@ -226,4 +274,4 @@ repository][squaremo-auto-commit].
 [cuttlefacts-app-repo]: https://github.com/cuttlefacts/cuttlefacts-app
 [github-fingerprints]: https://docs.github.com/en/github/authenticating-to-github/githubs-ssh-key-fingerprints
 [cuttlefacts-app-deployment]: https://github.com/cuttlefacts/cuttlefacts-app/blob/master/deploy/deployment.yaml
-[squaremo-auto-commit]: https://github.com/squaremo/cuttlefacts-app-automated/commit/ad445a6cbd938be4b93116990954104f5730177e
+[squaremo-auto-commit]: https://github.com/squaremo/cuttlefacts-app-auto-setters/commit/edb6e7c0724bcc2226dc3077558f747e7adfb8e8

api/v1alpha1/imageupdateautomation_types.go

@@ -62,6 +62,20 @@ type UpdateStrategy struct {
 	// given policy's image, to the policy's latest image reference.
 	// +optional
 	ImagePolicyRef *corev1.LocalObjectReference `json:"imagePolicyRef,omitempty"`
+	// Setters if present means update workloads using setters, via
+	// fields marked in the files themselves.
+	// +optional
+	Setters *SettersStrategy `json:"setters,omitempty"`
+}
+
+// SettersStrategy specifies how to use kyaml setters to update the
+// git repository.
+type SettersStrategy struct {
+	// Paths gives all paths that should be subject to updates using
+	// setters. If missing, the path `.` (the root of the git
+	// repository) is assumed.
+	// +optional
+	Paths []string `json:"paths,omitempty"`
 }
 
 // CommitSpec specifies how to commit changes to the git repository

config/crd/bases/image.toolkit.fluxcd.io_imageupdateautomations.yaml

@@ -99,6 +99,18 @@ spec:
                         TODO: Add other useful fields. apiVersion, kind, uid?'
                       type: string
                   type: object
+                setters:
+                  description: Setters if present means update workloads using setters,
+                    via fields marked in the files themselves.
+                  properties:
+                    paths:
+                      description: Paths gives all paths that should be subject to
+                        updates using setters. If missing, the path `.` (the root
+                        of the git repository) is assumed.
+                      items:
+                        type: string
+                      type: array
+                  type: object
               type: object
           required:
           - checkout

controllers/imageupdateautomation_controller.go

@@ -143,6 +143,18 @@ func (r *ImageUpdateAutomationReconciler) Reconcile(req ctrl.Request) (ctrl.Resu
 			}
 			return ctrl.Result{}, err
 		}
+	case updateStrat.Setters != nil:
+		// For setters we first want to compile a list of _all_ the
+		// policies in the same namespace (maybe in the future this
+		// could be filtered by the automation object).
+		var policies imagev1alpha1_reflect.ImagePolicyList
+		if err := r.List(ctx, &policies, &client.ListOptions{Namespace: req.NamespacedName.Namespace}); err != nil {
+			return ctrl.Result{}, err
+		}
+
+		if err := updateAccordingToSetters(ctx, tmp, policies.Items); err != nil {
+			return ctrl.Result{}, err
+		}
 	default:
 		log.Info("no update strategy given in the spec")
 		// no sense rescheduling until this resource changes
@@ -392,3 +404,9 @@ func updateAccordingToImagePolicy(ctx context.Context, path string, policy *imag
 	}
 	return update.UpdateImageEverywhere(path, path, latestRef, latestRef)
 }
+
+// updateAccordingToSetters updates files under the root by treating
+// the given image policies as kyaml setters.
+func updateAccordingToSetters(ctx context.Context, path string, policies []imagev1alpha1_reflect.ImagePolicy) error {
+	return update.UpdateWithSetters(path, path, policies)
+}

controllers/testdata/appconfig-expected/deploy.yaml

@@ -7,4 +7,4 @@ spec:
     spec:
       containers:
       - name: hello
-        image: helloworld:1.0.1
+        image: helloworld:1.0.1 # SETTER_SITE

controllers/testdata/appconfig-expected2/deploy.yaml

@@ -7,4 +7,4 @@ spec:
     spec:
       containers:
       - name: hello
-        image: helloworld:1.2.0
+        image: helloworld:1.2.0 # SETTER_SITE

controllers/testdata/appconfig-setters-expected/deploy.yaml

@@ -0,0 +1,10 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: test
+spec:
+  template:
+    spec:
+      containers:
+      - name: hello
+        image: helloworld:1.0.1 # SETTER_SITE

controllers/testdata/appconfig/deploy.yaml

@@ -7,4 +7,4 @@ spec:
     spec:
       containers:
       - name: hello
-        image: helloworld:1.0.0
+        image: helloworld:1.0.0 # SETTER_SITE