diff --git a/CHANGELOG.md b/CHANGELOG.md
index e25e67ee..498c0a39 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -20,11 +20,17 @@
 
 -->
 
+## v0.9.1
+
+**HOTFIX**
+
+f4b1936 removed proxy pod filter on feedback controller, which crashed the controller manager if normal pods were scheduled on nodes whose names were shorter than 10 characters, and added finalizers to normal pods (manual cleanup necessary!)
+
 ## v0.9.0
 
 ### New Features
 
-- Fix [#32](https://github.com/admiraltyio/multicluster-scheduler/issues/20). Config maps and secrets now follow pods. More specifically, if a proxy pod refers to config maps or secrets to be mounted as volumes, projected volumes, used as environment variables or, for secrets, as image pull secrets, Admiralty copies those config maps or secrets to the target cluster where the corresponding delegate pod runs.
+- Fix [#32](https://github.com/admiraltyio/multicluster-scheduler/issues/32). Config maps and secrets now follow pods. More specifically, if a proxy pod refers to config maps or secrets to be mounted as volumes, projected volumes, used as environment variables or, for secrets, as image pull secrets, Admiralty copies those config maps or secrets to the target cluster where the corresponding delegate pod runs.
 
 ## v0.8.2
 
diff --git a/README.md b/README.md
index a203d789..75b3f0c0 100644
--- a/README.md
+++ b/README.md
@@ -77,7 +77,7 @@ kubectl --context "$CLUSTER2" create namespace admiralty
 helm install multicluster-scheduler admiralty/multicluster-scheduler \
   --kube-context "$CLUSTER2" \
   --namespace admiralty \
-  --version 0.9.0 \
+  --version 0.9.1 \
   --set clusterName=c2
 ```
 
@@ -103,7 +103,7 @@ kubectl --context "$CLUSTER1" create namespace admiralty
 helm install multicluster-scheduler admiralty/multicluster-scheduler \
   --kube-context "$CLUSTER1" \
   --namespace admiralty \
-  --version 0.9.0 \
+  --version 0.9.1 \
   --set clusterName=c1 \
   --set targetSelf=true \
   --set targets[0].name=c2
@@ -303,7 +303,7 @@ jq '.targets += [{name: "c2"}]' | \
 helm upgrade multicluster-scheduler admiralty/multicluster-scheduler \
   --kube-context "$CLUSTER1" \
   --namespace admiralty \
-  --version 0.9.0 \
+  --version 0.9.1 \
   -f -
 ```
 
diff --git a/charts/multicluster-scheduler/Chart.yaml b/charts/multicluster-scheduler/Chart.yaml
index 6853425e..f0f5a8c3 100644
--- a/charts/multicluster-scheduler/Chart.yaml
+++ b/charts/multicluster-scheduler/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v2
 name: multicluster-scheduler
-version: 0.9.0
+version: 0.9.1
 #kubeVersion: A SemVer range of compatible Kubernetes versions (optional)
 description: A system of Kubernetes controllers that intelligently schedules workloads across clusters.
 type: application
@@ -14,5 +14,5 @@ home: https://github.com/admiraltyio/multicluster-scheduler
 #    email: The maintainer's email (optional for each maintainer)
 #    url: A URL for the maintainer (optional for each maintainer)
 icon: https://admiralty.io/icons/icon-144x144.png
-appVersion: 0.9.0
+appVersion: 0.9.1
 #deprecated: Whether this chart is deprecated (optional, boolean)
diff --git a/charts/multicluster-scheduler/README.md b/charts/multicluster-scheduler/README.md
index 13b431b2..3c6ad966 100644
--- a/charts/multicluster-scheduler/README.md
+++ b/charts/multicluster-scheduler/README.md
@@ -46,7 +46,7 @@ Create a namespace for multicluster-scheduler and install the chart in it, using
 ```sh
 kubectl create namespace admiralty
 helm install multicluster-scheduler admiralty/multicluster-scheduler \
-  --version 0.9.0 \
+  --version 0.9.1 \
   -n admiralty \
   -f values.yaml
 ```
@@ -109,7 +109,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit
 | targets[].context | string | `""` | if using a custom kubeconfig secret, with multiple contexts, override the kubeconfig's current context |
 | imagePullSecretName | string | `""` |  |
 | controllerManager.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-agent"` |  |
-| controllerManager.image.tag | string | `"0.9.0"` |  |
+| controllerManager.image.tag | string | `"0.9.1"` |  |
 | controllerManager.image.pullPolicy | string | `"IfNotPresent"` |  |
 | controllerManager.resources | object | `{}` |  |
 | controllerManager.nodeSelector | object | `{}` |  |
@@ -117,7 +117,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit
 | controllerManager.affinity | object | `{}` |  |
 | controllerManager.tolerations | array | `[]` |  |
 | scheduler.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-scheduler"` |  |
-| scheduler.image.tag | string | `"0.9.0"` |  |
+| scheduler.image.tag | string | `"0.9.1"` |  |
 | scheduler.image.pullPolicy | string | `"IfNotPresent"` |  |
 | scheduler.resources | object | `{}` |  |
 | scheduler.nodeSelector | object | `{}` |  |
@@ -125,7 +125,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit
 | scheduler.affinity | object | `{}` |  |
 | scheduler.tolerations | array | `[]` |  |
 | postDeleteJob.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-remove-finalizers"` |  |
-| postDeleteJob.image.tag | string | `"0.9.0"` |  |
+| postDeleteJob.image.tag | string | `"0.9.1"` |  |
 | postDeleteJob.image.pullPolicy | string | `"IfNotPresent"` |  |
 | postDeleteJob.resources | object | `{}` |  |
 | postDeleteJob.nodeSelector | object | `{}` |  |