The ClusterRoleBinding was created only after the followers were deployed
but there's no reason that it will be created then and not right after we
create the ClusterRole.
Furthermore, it was created for a new service-account that was named conjur
and was never used. This means that it didn't do anything and the only reason why
we didn't see issues is that the docs tell customers to do it manually (while there's
no reason they should) and consuming projects (e.g secrets-provider-for-k8s, conjur-authn-k8s-client)
created the correct ClusterRoleBinding on their own.
The ClusterRoleBinding was created only after the followers were deployed but there's no reason that it will be created then and not right after we create the ClusterRole.
Furthermore, it was created for a new service-account that was named
conjurand was never used. This means that it didn't do anything and the only reason why we didn't see issues is that the docs tell customers to do it manually (while there's no reason they should) and consuming projects (e.gsecrets-provider-for-k8s,conjur-authn-k8s-client) created the correct ClusterRoleBinding on their own.