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
EPMDEDP-17305: fix: Reduce the operator's RBAC to the permissions it uses
Every grant is backed by a call site.
1. The chart ships no cluster-scoped RBAC. The ServiceAccount holds one
namespaced Role and one RoleBinding.
2. Verbs are explicit per resource: secrets get;list;watch;update;delete;
configmaps, quicklinks and triggertemplates get; ingresses, httproutes and
routes get;create; cdpipelines and stages get;list; pipelineruns
list;watch;create; eventlisteners get;create;patch; leases
create;get;update; /status get;patch;update; /finalizers update.
3. The cache holds only Secrets labelled app.edp.epam.com/integration-secret,
the one type a controller watches. Everything else is read live through
client.Cache.DisableFor, so no informer starts and no list/watch is needed.
DefaultTransform strips managedFields.
4. The kubebuilder markers are the single source of truth. controller-gen
emits a namespaced Role only; both chart Roles mirror config/rbac/role.yaml
and differ solely by the platform split.
5. The kustomize path mirrors the chart: manager-role bound by a RoleBinding,
carrying leader-election leases and events, plus metrics-auth for the
metrics endpoint that config/default enables.
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
0 commit comments