You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For optimization purposes operator was creating a cache map to remember
if service accounts and role binding was deployed to a namespace. This
could lead to a problem, when a namespace was deleted, since this
cache was not synchronized. For the sake of correctness remove the
cache, and check every time if required service account and rbac is
present. In the normal case this introduces an overhead of two API calls
per an event (one to get a service accounts, one to get a role binding),
which should not be a problem, unless proven otherwise.
Ensures the pod service account and role bindings exists in a namespace before a PG cluster is created there so that a user does not have to deploy these credentials manually.
497
-
StatefulSets require the service account to create pods; Patroni requires relevant RBAC bindings to access endpoints.
496
+
Ensures the pod service account and role bindings exists in a namespace
497
+
before a PG cluster is created there so that a user does not have to deploy
498
+
these credentials manually. StatefulSets require the service account to
499
+
create pods; Patroni requires relevant RBAC bindings to access endpoints.
498
500
499
501
The operator does not sync accounts/role bindings after creation.
0 commit comments