feat: all-in-one manifests migrations job improvement

CHANGELOG.md

@@ -160,6 +160,11 @@ Adding a new version? You'll need three changes:
 - Gateway's `AttachedRoutes` fields get updated with the number of routes referencing
   and using each listener.
   [#4052](https://github.com/Kong/kubernetes-ingress-controller/pull/4052)
+- `all-in-one-postgres.yaml` and `all-in-one-postgres-enterprise.yaml` manifests'
+  migrations job now works properly when running against an already bootstrapped
+  database, allowing upgrades from one version of Kong Gateway to another without
+  tearing down the database.
+  [#4116](https://github.com/Kong/kubernetes-ingress-controller/pull/4116)
 
 ### Changed
 

config/variants/postgres/migration.yaml

@@ -28,5 +28,5 @@ spec:
           value: postgres
         - name: KONG_PG_PORT
           value: "5432"
-        command: [ "/bin/bash", "-c", "kong migrations bootstrap" ]
+        command: [ "/bin/bash", "-c", "kong migrations bootstrap && kong migrations up && kong migrations finish" ]
       restartPolicy: OnFailure

deploy/single/all-in-one-postgres-enterprise.yaml

@@ -1923,7 +1923,7 @@ spec:
       - command:
         - /bin/bash
         - -c
-        - kong migrations bootstrap
+        - kong migrations bootstrap && kong migrations up && kong migrations finish
         env:
         - name: KONG_LICENSE_DATA
           valueFrom:

deploy/single/all-in-one-postgres.yaml

@@ -1860,7 +1860,7 @@ spec:
       - command:
         - /bin/bash
         - -c
-        - kong migrations bootstrap
+        - kong migrations bootstrap && kong migrations up && kong migrations finish
         env:
         - name: KONG_PG_PASSWORD
           value: kong