You should first investigate if you can use RBAC to accomplish what you want.  If you can't, you use isi_visudo.  There's a background process that will detect that you've made custom changes (via isi_visudo) and will automatically re-merge your custom content with the auto-generated content based on your RBAC configuration.  Your custom content is stored in /etc/mcp/override/sudoers (but use isi_visudo, don't edit this file by hand).  The system content is stored in /etc/mcp/templates/sudoers.  These 2 files along with your RBAC configuration are merged to create the final config that's stored in /usr/local/etc/sudoers; this is the file used by sudo to evaluate if you have permissions to run a given command.
Community,  I am trying to configure the cluster to allow our storage admin like myself to be able to use commands that require a sudo from the CLI.  I was able to configure my other clusters running both OneFS 7.0.1.4 and 7.0.2.1 by editing the sudoers file found under /usr/local/etc.  I just added the Administrators local group to the file like so:  # Defaults!/sbin/reboot !log_output  ## ## Runas alias specification ##  ## ## User privilege specification ## root ALL=(ALL) ALL  ## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL  ## Same thing without a password # %wheel ALL=(ALL) NOPASSWD: ALL  ## Uncomment to allow members of group sudo to execute any command # %sudo ALL=(ALL) ALL %Administrators ALL=(ALL)       ALL  ## Uncomment to allow any user to run sudo if they know the password ## of the user they are running the command as (root by default). # Defaults targetpw  # Ask for the password of the target user # ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'  Well after installing 7.1.0.5 on this new cluster we just received:   Question: 
Sudoers File on Cluster