Skip to content

local role becomes cluster role when operator is deployed. #874

@raffaelespazzoli

Description

@raffaelespazzoli

I have an operator defined by the attached CSV
cert-utils-operator.zip

The thing to notice is that this operator has both a role and a cluster role.

when I make it available through the operator hub the attached install plan is created. At this point I still can see that there are two roles, one is local and on is a cluster role.

when the operator is deployed three roles are created:

  1. local role
  2. cluster roles: the correct one and a clusterrole version of the local role.

this shoudl clarify what I mean:

image

Also the corresponding bindings to the operator service accounts are created.

This should not happen. However I am not sure if I am doing something wrong or if this is a bug.

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