diff --git a/.github/openshift/community-operators-prod b/.github/openshift/community-operators-prod
new file mode 100644
index 0000000..911e326
--- /dev/null
+++ b/.github/openshift/community-operators-prod
@@ -0,0 +1,45 @@
+ Thanks submitting your Operator. Please check below list before you create your Pull Request.
+
+ ### New Submissions
+ * [ ]  Are you familiar with our [contribution guidelines](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-via-pr.md)?
+ * [ ]  Have you [packaged and deployed](https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md) your Operator for Operator Framework?
+ * [ ]  Have you tested your Operator with all Custom Resource Definitions?
+ * [ ]  Have you tested your Operator in all supported [installation modes](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/building-your-csv.md#operator-metadata)?
+ * [ ]  Have you considered whether you want use [semantic versioning order](https://github.com/operator-framework/community-operators/blob/master/docs/operator-ci-yaml.md#semver-mode)?
+ * [ ]  Is your submission [signed](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-prerequisites.md#sign-your-work)?
+ * [ ]  Is operator [icon](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#operator-icon) set?
+
+ ### Updates to existing Operators
+ * [x]  Did you create a `ci.yaml` file according to the [update instructions](https://github.com/operator-framework/community-operators/blob/master/docs/operator-ci-yaml.md)?
+ * [x]  Is your new CSV pointing to the previous version with the `replaces` property if you chose `replaces-mode` via the `updateGraph` property in `ci.yaml`?
+ * [x]  Is your new CSV referenced in the [appropriate channel](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#channels) defined in the `package.yaml` or `annotations.yaml` ?
+ * [x]  Have you tested an update to your Operator when deployed via OLM?
+ * [x]  Is your submission [signed](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-prerequisites.md#sign-your-work)?
+
+ ### Your submission should not
+ * [x]  Modify more than one operator
+ * [x]  Modify an Operator you don't own
+ * [x]  Rename an operator - please remove and add with a different name instead
+ * [x]  Modify any files outside the above mentioned folders
+ * [x]  Contain more than one commit. **Please squash your commits.**
+
+ ### Operator Description must contain (in order)
+ 1. [x]  Description about the managed Application and where to find more information
+ 2. [x]  Features and capabilities of your Operator and how to use it
+ 3. [x]  Any manual steps about potential pre-requisites for using your Operator
+
+ ### Operator Metadata should contain
+ * [x]  Human readable name and 1-liner description about your Operator
+ * [x]  Valid [category name](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#categories)1
+ * [x]  One of the pre-defined [capability levels](https://github.com/operator-framework/operator-courier/blob/4d1a25d2c8d52f7de6297ec18d8afd6521236aa2/operatorcourier/validate.py#L556)2
+ * [x]  Links to the maintainer, source code and documentation
+ * [x]  Example templates for all Custom Resource Definitions intended to be used
+ * [x]  A quadratic logo
+
+ Remember that you can preview your CSV [here](https://operatorhub.io/preview).
+
+ --
+
+ 1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
+
+ 2 For more information see [here](https://sdk.operatorframework.io/docs/overview/#operator-capability-level)
diff --git a/.github/operatorhub/community-operators b/.github/operatorhub/community-operators
new file mode 100644
index 0000000..5b71e16
--- /dev/null
+++ b/.github/operatorhub/community-operators
@@ -0,0 +1,45 @@
+ Thanks submitting your Operator. Please check below list before you create your Pull Request.
+ 
+ ### New Submissions
+ * [ ]  Are you familiar with our [contribution guidelines](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-via-pr.md)?
+ * [ ]  Have you [packaged and deployed](https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md) your Operator for Operator Framework?
+ * [ ]  Have you tested your Operator with all Custom Resource Definitions?
+ * [ ]  Have you tested your Operator in all supported [installation modes](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/building-your-csv.md#operator-metadata)?
+ * [ ]  Have you considered whether you want use [semantic versioning order](https://github.com/operator-framework/community-operators/blob/master/docs/operator-ci-yaml.md#semver-mode)?
+ * [ ]  Is your submission [signed](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-prerequisites.md#sign-your-work)?
+ * [ ]  Is operator [icon](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#operator-icon) set?
+ 
+ ### Updates to existing Operators
+ * [x]  Did you create a `ci.yaml` file according to the [update instructions](https://github.com/operator-framework/community-operators/blob/master/docs/operator-ci-yaml.md)?
+ * [x]  Is your new CSV pointing to the previous version with the `replaces` property if you chose `replaces-mode` via the `updateGraph` property in `ci.yaml`?
+ * [x]  Is your new CSV referenced in the [appropriate channel](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#channels) defined in the `package.yaml` or `annotations.yaml` ?
+ * [x]  Have you tested an update to your Operator when deployed via OLM?
+ * [x]  Is your submission [signed](https://github.com/operator-framework/community-operators/blob/master/docs/contributing-prerequisites.md#sign-your-work)?
+ 
+ ### Your submission should not
+ * [x]  Modify more than one operator
+ * [x]  Modify an Operator you don't own
+ * [x]  Rename an operator - please remove and add with a different name instead
+ * [x]  Modify any files outside the above mentioned folders
+ * [x]  Contain more than one commit. **Please squash your commits.**
+ 
+ ### Operator Description must contain (in order)
+ 1. [x]  Description about the managed Application and where to find more information
+ 2. [x]  Features and capabilities of your Operator and how to use it
+ 3. [x]  Any manual steps about potential pre-requisites for using your Operator
+ 
+ ### Operator Metadata should contain
+ * [x]  Human readable name and 1-liner description about your Operator
+ * [x]  Valid [category name](https://github.com/operator-framework/community-operators/blob/master/docs/packaging-operator.md#categories)1
+ * [x]  One of the pre-defined [capability levels](https://github.com/operator-framework/operator-courier/blob/4d1a25d2c8d52f7de6297ec18d8afd6521236aa2/operatorcourier/validate.py#L556)2
+ * [x]  Links to the maintainer, source code and documentation
+ * [x]  Example templates for all Custom Resource Definitions intended to be used
+ * [x]  A quadratic logo
+ 
+ Remember that you can preview your CSV [here](https://operatorhub.io/preview).
+ 
+ --
+ 
+ 1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
+ 
+ 2 For more information see [here](https://sdk.operatorframework.io/docs/overview/#operator-capability-level)
diff --git a/.github/workflows/release-pipeline.yml b/.github/workflows/release-pipeline.yml
index 2015d3a..92579ba 100644
--- a/.github/workflows/release-pipeline.yml
+++ b/.github/workflows/release-pipeline.yml
@@ -166,7 +166,7 @@ jobs:
           name: bundle-${{ github.event.inputs.operator_version }}.tgz
           path: "${{ runner.temp }}"
           
-      - name: "Create and prepare branch for k8s-operator"
+      - name: "Create, prepare branch and open PR for k8s-operator"
         env:
           BRANCH_NAME: "kaoto-operator.${{ github.event.inputs.operator_version }}"
           GH_TOKEN: ${{ secrets.PR_TOKEN }}
@@ -190,6 +190,7 @@ jobs:
           git commit -m "operator kaoto-operator (${{ github.event.inputs.operator_version }})"
           
           git push -u origin ${BRANCH_NAME}
+          gh pr create --title "operator kaoto (${{ github.event.inputs.operator_version }})" -F ../.github/operatorhub/community-operators -R k8s-operatorhub/community-operators
 
   prepare-openshift-operator-branch:
     permissions:
@@ -207,13 +208,13 @@ jobs:
           token: ${{ secrets.PR_TOKEN }}
           ref: main
 
-      - name: "🛰️ Download Bundle"
+      - name: "🛰️ Download UI Dist"
         uses: actions/download-artifact@v4
         with:
           name: bundle-${{ github.event.inputs.operator_version }}.tgz
           path: "${{ runner.temp }}"
           
-      - name: "Create and prepare branch for k8s-operator"
+      - name: "Create, prepare branch and open PR for community-operators-prod"
         env:
           BRANCH_NAME: "kaoto-operator.${{ github.event.inputs.operator_version }}"
           GH_TOKEN: ${{ secrets.PR_TOKEN }}
@@ -238,3 +239,4 @@ jobs:
           git commit -m "operator kaoto-operator (${{ github.event.inputs.operator_version }})"
           
           git push -u origin ${BRANCH_NAME}
+          gh pr create --title "operator kaoto (${{ github.event.inputs.operator_version }})" -F ../.github/openshift/community-operators-prod -R redhat-openshift-ecosystem/community-operators-prod