Skip to content

Scope UDS Operator RBAC #2278

@mjnagel

Description

@mjnagel

Currently the UDS Operator uses the default RBAC Mode of Pepr, admin. Admin mode provides cluster admin permissions which is overly permissive for what we need.

We should scope our access for the UDS Operator (and policy/admission pods) to only the required access. Note that this WILL require us to do more than just flip to scoped since the scoped method will only take into account Watches and Reconciles. We will also need to "audit" the other resources and actions we need for other K8s calls (ex: creating/deleting virtualservices). This should be clear through testing and the code where permissions are needed.

There may be some timing/"how" considerations since we currently use a dynamically generated chart for Pepr. We will likely want to "post-process" and replace the upstream roles/bindings before creating the zarf package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions