Leftover RBAC from previous multicluster approach?

[alpeb]

linkerd multicluster install is producing a SA linkerd-service-mirror-remote-access-default tied to a role to list/get/watch services and getting linkerd-config. This is also produced by linkerd multicluster allow (basically this template).
It seems to me this is a leftover from the previous multicluster installation, as access to a target cluster is now granted through linkerd multicluster link and is using different permissions. Is that correct?

CC @adleong @zaharidichev

[alpeb]

Never mind, I just saw that RBAC is used by the kubeconfig encoded in the secret produced by linkerd mc link