-
Bug
-
Resolution: Done
-
Medium
-
Istanbul Release, Jakarta Release
-
None
When deploying cps chart, cps-core is not starting because its cps-core-readiness init container is not able to complete and it keeps failing with the error:
2022-01-21 20:26:52,366 - INFO - Checking if cps-core-postgres is ready 2022-01-21 20:26:54,260 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': 'f03d45c8-2c7a-48d8-9767-678d5e2ff909', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'Date': 'Fri, 21 Jan 2022 20:26:54 GMT', 'Content-Length': '539'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"replicasets.apps \"rockhoppers-cps-core-postgres-primary-764d555c77\" is forbidden: User \"system:serviceaccount:rockhoppers:rockhoppers-cps-core-read\" cannot get resource \"replicasets/status\" in API group \"apps\" in the namespace \"rockhoppers\": RBAC: role.rbac.authorization.k8s.io \"rockhoppers-read\" not found","reason":"Forbidden","details":{"name":"rockhoppers-cps-core-postgres-primary-764d555c77","group":"apps","kind":"replicasets"},"code":403}
RBAC role for reading and retrieving status is not defined.