ClusterRole about dynatrace-operator HOT 3 CLOSED

this is fixed in main: #1881

but those service accounts are really old, that is why their names are confusing (there use to be a reason for having multiple service accounts, but no longer)

and the privileged SCC is "needed" because we only want to use built in SCCs (custom ones just caused confusion), AND the privileged SCC is the only built-in SCC that allows csi volumes. (maybe in openshift 4.13 this changes)

from dynatrace-operator.

Hi

Thanks for the fast answer !

For the duplicated scc in yaml files I made a mistake in the file names.

https://github.com/Dynatrace/dynatrace-operator/releases/download/0.12.0/openshift.yaml
and
https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.12.0/openshift-csi.yaml

The ClusterRoles and ClusterRoleBindings

• dynatrace-activegate
• dynatrace-dynakube-oneagent-privileged

are defined in both yaml files.

from dynatrace-operator.

We've identified the problem and will fix it in future releases. Since it's the same resources in openshfit.yaml and openshift-csi.yaml there should not be a problem with applying it more than once.

The privileged/unprivileged naming mismatch will be combined into a single resource in the future.

from dynatrace-operator.