# The certified variant of the operator (2.5) does not provide cluster-wide functionality in OpenShift

**URL:** <https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554>\
**Category:** Percona Operator for PostgreSQL\
**Created:** [December 9, 2024, 12:52pm UTC](https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554 "2024-12-09T12:52:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![92fnko](https://avatars.discourse-cdn.com/v4/letter/9/a698b9/32.png) [@92fnko](https://forums.percona.com/u/92fnko)\
**Post date:** [December 9, 2024, 12:52pm UTC](https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554/1 "2024-12-09T12:52:27Z")

</div>

## Description:

From my understanding, 2.5 brings cluster-wide functionality (possible to watch all namespaces) to the PostgreSQL Operator, but when I try to install the certified operator via OperatorHub in OpenShift, the `All namespaces on the cluster (default)` option can’t be chosen, but if I instead choose the community variant via OperatorHub, this is possible. Is there a particular reason for this?

## Steps to Reproduce:

See the above.

## Version:

2.5

## Logs:

n/a

## Expected Result:

The certified operator should be able to run in cluster-wide mode.

## Actual Result:

The certified operator can only monitor the namespace it’s deployed to.

## Additional Information:

n/a

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [December 9, 2024, 3:09pm UTC](https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554/2 "2024-12-09T15:09:36Z")

</div>

Hi @92fnko, did you check this catalog [https://catalog.redhat.com/software/containers/percona/percona-postgresql-operator-bundle-marketplace/61c194e917f914cd723304fa](https://catalog.redhat.com/software/containers/percona/percona-postgresql-operator-bundle-marketplace/61c194e917f914cd723304fa)?

---

<div class="post-metadata">

**Author:** ![92fnko](https://avatars.discourse-cdn.com/v4/letter/9/a698b9/32.png) [@92fnko](https://forums.percona.com/u/92fnko)\
**Post date:** [December 9, 2024, 4:23pm UTC](https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554/3 "2024-12-09T16:23:32Z")

</div>

@Slava_Sarzhan I didn’t know there was a second channel (stable-cw) for the cluster-wide variant. Is this documented somewhere? 🙂

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [December 11, 2024, 5:57pm UTC](https://forums.percona.com/t/the-certified-variant-of-the-operator-2-5-does-not-provide-cluster-wide-functionality-in-openshift/35554/4 "2024-12-11T17:57:03Z")

</div>

> [@92fnko](#):
>
> stable-cw

@92fnko we have a task [Jira](https://perconadev.atlassian.net/browse/K8SPG-689) to document it.