Separation of service accounts for Velero deployment and node-agent

[ugur99]

Describe the problem/challenge you have Currently, both the Velero deployment and the node-agent in the Helm chart share the same ServiceAccount, which grants extensive permissions nearly equivalent to cluster-admin. While Velero likely requires these permissions for its backup and restore operations, the node-agent might not need such a wide range of permissions

Describe the solution you'd like To improve security and adhere to the principle of least privilege, it would be beneficial to evaluate the specific permissions required by each component and create separate ServiceAccounts with appropriate, fine-grained permissions.