diff --git a/_posts/2023-07-01-renovate-bot-kubernetes.md b/_posts/2023-07-01-renovate-bot-kubernetes.md
index d83a0baf0f..bef99297b0 100644
--- a/_posts/2023-07-01-renovate-bot-kubernetes.md
+++ b/_posts/2023-07-01-renovate-bot-kubernetes.md
@@ -117,6 +117,24 @@ So we’ll need to `git pull` to get latest and we should see our Renovate confi
 ```
 {: file="renovate.json" }
 
+If you're using FluxCD ([as shown here](/posts/flux-devops-gitops)) you also want add the `flux` extension and filematch. This will allow Renovate to scan your FluxCD manifests as well as creating Pull Requests for your Helm chart versions.
+
+```json
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:base"
+  ],
+  "flux": {
+    "fileMatch": ["\\.yml$"]
+  },
+  "kubernetes": {
+    "fileMatch": ["\\.yml$"]
+  }
+}
+```
+{: file="renovate.json" }
+
 Once we’ve made that change to our config locally, we’ll then commit that change and push it up.
 
 Once we push this change up and it scans our repo, we can see a new [issue that was created](https://github.com/techno-tim/k8s-renovate/issues/2)!  This is a special type of issue that Renovate creates for us and it is kind of like a dashboard for all of our dependencies.