prepare release v1.44.0 (#2108)

charts/fdb-operator/Chart.yaml

@@ -18,6 +18,6 @@ type: application
 version: 0.2.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application.
-appVersion: v1.43.0
+appVersion: v1.44.0
 maintainers:
   - name: "foundationdb-ci"

charts/fdb-operator/values.yaml

@@ -1,7 +1,7 @@
 ---
 image:
   repository: foundationdb/fdb-kubernetes-operator
-  tag: v1.43.0
+  tag: v1.44.0
   pullPolicy: IfNotPresent
 initContainers:
   6.2:

config/deployment/manager.yaml

@@ -83,7 +83,7 @@ spec:
       containers:
         - command:
             - /manager
-          image: foundationdb/fdb-kubernetes-operator:v1.43.0
+          image: foundationdb/fdb-kubernetes-operator:v1.44.0
           name: manager
           env:
             - name: WATCH_NAMESPACE

config/samples/deployment.yaml

@@ -178,7 +178,7 @@ spec:
           valueFrom:
             fieldRef:
               fieldPath: metadata.namespace
-        image: foundationdb/fdb-kubernetes-operator:v1.43.0
+        image: foundationdb/fdb-kubernetes-operator:v1.44.0
         name: manager
         ports:
         - containerPort: 8080

docs/changelog/v1.44.0.md

@@ -0,0 +1,10 @@
+# v1.44.0
+
+## Changes
+
+### Operator
+
+* Fix the update status setup when a different image type is used [#2106](https://github.com/FoundationDB/fdb-kubernetes-operator/pull/2106)
+* Fix typo in documentation mention of redundancy_mode [#2104](https://github.com/FoundationDB/fdb-kubernetes-operator/pull/2104)
+* Update examples for imageType setting [#2102](https://github.com/FoundationDB/fdb-kubernetes-operator/pull/2102)
+* Make sure to test if the fdb-kubernetes-monitor is able to update the annotation after the partition [#2096](https://github.com/FoundationDB/fdb-kubernetes-operator/pull/2096)