# Release Date Percona Operator for PostgreSQL 2.0.0 **URL:** \ **Category:** Percona Operator for PostgreSQL\ **Created:** [February 23, 2023, 8:33am UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247 "2023-02-23T08:33:44Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sasi](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sasi](https://forums.percona.com/u/sasi)\ **Post date:** [February 23, 2023, 8:33am UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/1 "2023-02-23T08:33:44Z")
Hi there! First things first: Thanks for the community and all your work. šŸ™‚ Regarding Percona Operator for PostgreSQL 2.0.0: Iā€™m looking forward to an official release of the Helmchart for it. Can I support the tech preview somehow and test things and give feedback somewhere? If I understood the changes correctly then that a possible upgrade path from 1.3.0 to 2.0.0 is quite breaking (?). I could imagine to try out some possibilities and share my experience on the GitHub repository for it. Thanks in Advance and have a happy Thursday! ---
**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:** [February 23, 2023, 2:53pm UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/2 "2023-02-23T14:53:27Z")
Hi @sasi, We do not have official helm chart for PostgreSQL 2.0.0. We will create it in next release. We are waiting for your feedback. You can find official documentation here: > **[Percona Operator for PostgreSQL](https://docs.percona.com/percona-operator-for-postgresql/2.0/index.html)** > > Kubernetes have added a way to manage containerized systems, including database > clusters. This management is achieved by controllers, declared in configuration > files. These controllers provide automation with the ability to create objects, > such as a... GitHub repo: > **[GitHub - percona/percona-postgresql-operator at v2.0.0](https://github.com/percona/percona-postgresql-operator/tree/v2.0.0)** > > v2.0.0 If you have any feedback about docs or the operator itself, feel free to create tasks for us. Jira project is [K8SPG](https://jira.percona.com/projects/K8SPG) . > If I understood the changes correctly, then that a possible upgrade path from 1.3.0 to 2.0.0 is quite breaking (?). We have a plan to create a migration procedure and it will be possible to migrate from v1.x to v2.x. ---
**Author:** ![sasi](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sasi](https://forums.percona.com/u/sasi)\ **Post date:** [February 23, 2023, 4:28pm UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/3 "2023-02-23T16:28:38Z")
Nice! Thanks for the links. Iā€™ll come back with feedback! ---
**Author:** ![sasi](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sasi](https://forums.percona.com/u/sasi)\ **Post date:** [March 1, 2023, 4:16pm UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/4 "2023-03-01T16:16:34Z")
Just a heads up. I like your operator improvements! Iā€™m trying to figure out, how you restructured your CRDs, which is obvious, but there are just some background infos iā€™m missing. I tested the s3-backup strategies and new cluster creation with existing backups and it works like a charm. The change to statefulsets with instance-management instead of replica-management is also awesome. iā€™m not fully through the global-configs vs. specific configs; they seem not quite connected. Still working on my knowledge for that. šŸ˜ƒ iā€™m sitting on some migration ideas, as you change from [pg.percona.com/v1](http://pg.percona.com/v1) to [pg.percona.com/v2beta1](http://pg.percona.com/v2beta1) but all in all, i can see some solutions already. Happy to share my insights, if you like! ---
**Author:** ![Sergey\_Zhuravlev](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_zhuravlev/32/6410_2.png) [@Sergey\_Zhuravlev](https://forums.percona.com/u/Sergey_Zhuravlev)\ **Post date:** [March 31, 2023, 4:45pm UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/5 "2023-03-31T16:45:20Z")
Not work as describe in manual # Install Percona Distribution for PostgreSQL using Helm helm install my-operator percona/pg-operator --version 2.0.0 Error: INSTALLATION FAILED: chart ā€œpg-operatorā€ matching 2.0.0 not found in percona index. (try ā€˜helm repo updateā€™): no chart version found for pg-operator-2.0.0 ---
**Author:** ![Sergey\_Zhuravlev](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_zhuravlev/32/6410_2.png) [@Sergey\_Zhuravlev](https://forums.percona.com/u/Sergey_Zhuravlev)\ **Post date:** [March 31, 2023, 5:07pm UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/6 "2023-03-31T17:07:49Z")
If install on minicube as: # Install Percona Distribution for PostgreSQL on Kubernetes ```auto orbit@orbit-dp pgo_v2]$ kubectl apply -f deploy/bundle.yaml customresourcedefinition.apiextensions.k8s.io/perconapgbackups.pg.percona.com configured Warning: resource customresourcedefinitions/perconapgclusters.pg.percona.com is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically. customresourcedefinition.apiextensions.k8s.io/perconapgrestores.pg.percona.com configured serviceaccount/percona-postgresql-operator created role.rbac.authorization.k8s.io/percona-postgresql-operator created rolebinding.rbac.authorization.k8s.io/service-account-percona-postgresql-operator created deployment.apps/percona-postgresql-operator created Error from server (Invalid): error when applying patch: {"metadata":{"annotations":{"controller-gen.kubebuilder.io/version":"v0.8.0","kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"apiextensions.k8s.io/v1\",\"kind\":\"CustomResourceDefinition\",\"metadata\":{\"annotations\":{\"controller-gen.kubebuilder.io/version\":\"v0.8.0\"},\"creationTimestamp\":null,\"name\":\"perconapgclusters.pg.percona.com\"},\"spec\":{\"gr ``` and at end ```auto Resource: "apiextensions.k8s.io/v1, Resource=customresourcedefinitions", GroupVersionKind: "apiextensions.k8s.io/v1, Kind=CustomResourceDefinition" Name: "perconapgclusters.pg.percona.com", Namespace: "" for: "deploy/bundle.yaml": error when patching "deploy/bundle.yaml": CustomResourceDefinition.apiextensions.k8s.io "perconapgclusters.pg.percona.com" is invalid: [metadata.annotations: Too long: must have at most 262144 bytes, status.storedVersions[0]: Invalid value: "v1": must appear in spec.versions] Error from server (Invalid): error when creating "deploy/bundle.yaml": CustomResourceDefinition.apiextensions.k8s.io "postgresclusters.postgres-operator.crunchydata.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes ``` ```auto [orbit@orbit-dp pgo_v2]$ kubectl -n postgres-operator get po NAME READY STATUS RESTARTS AGE percona-postgresql-operator-66d787fcc4-hvlb4 1/1 Running 0 80s ``` ---
**Author:** ![Sergey\_Zhuravlev](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_zhuravlev/32/6410_2.png) [@Sergey\_Zhuravlev](https://forums.percona.com/u/Sergey_Zhuravlev)\ **Post date:** [April 3, 2023, 8:51am UTC](https://forums.percona.com/t/release-date-percona-operator-for-postgresql-2-0-0/20247/7 "2023-04-03T08:51:02Z")
Regarding my two posts above - there is a solution) Iā€™m sorry I tried to act as described in the README.md file. This works to run and get the first view.