Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crunchy Postgres missing RBAC rule leading to status: "Failed Up to date" #3224

Open
muellerfabi opened this issue Dec 7, 2023 · 1 comment

Comments

@muellerfabi
Copy link

We have deployed Crunchy Postgres Operator 5.4.1 with scoped permissions according to https://docs.openshift.com/container-platform/4.12/operators/admin/olm-creating-policy.html

The rules listed in .spec.install.spec.permissions.0.rules in CSV were used to create the role that is bound to the scoped serviceaccount.

Now after a while we noticed that the installed operator shows status "Failed Up to date".
CSVshows the following status:
install strategy failed: install strategy failed: deployments.apps "pgo" is forbidden: User "system:serviceaccount:postgres-operator:scoped" cannot update resource "deployments" in API group "apps" in the namespace "postgres-operator"

Adding update to the role fixes the issue.

Suggestion: insert update here: https://github.com/redhat-openshift-ecosystem/certified-operators/blob/main/operators/crunchy-postgres-operator/5.5.0/manifests/crunchy-postgres-operator.clusterserviceversion.yaml#L355

@muellerfabi
Copy link
Author

CC @tony-landreth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant