Closed dharmit closed 3 years ago
Hi @dharmit,
I have no time to do that. However, if you be able to do it your contribution is very welcome. I'd recommend migrate the project to use the latest version of SDK, by following the doc: https://sdk.operatorframework.io/docs/building-operators/golang/migration/
Then, we need to generate the bundle and publish it in: https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators and in: https://github.com/operator-framework/community-operators
Would you like to help out? I can review your contributions.
Hi @camilamacedo86. Unfortunately, I'm in a tight spot as well and can't help with the effort at this point. 😞
Question
What did you do?
Tried to install the Operator on OCP 4.9 using steps mentioned in https://github.com/openshift/odo/issues/4961.
What did you expect to see?
Operator to get installed and available for use
What did you see instead? Under which circumstances?
Copied from bugzilla
Environment
~* postgresql-operator version:
0.1.1 (Current)
(used the one from https://operatorhub.io/operator/postgresql-operator-dev4devs-com)~(Confused above with minikube)
Additional context
Looking at https://github.com/redhat-openshift-ecosystem/community-operators-prod/discussions/138, it seems like the PostgreSQL Operator will no longer be installed on OCP 4.9 as it uses
v1beta1
API. Are there plans to upgrade the Operator to usev1
API?