Will be good to put clean of files inside /tmp/sysdig-agent* after install else other users will not be able to install

As different user on same system,it fails without any error.Looks like as say user coopnonprod-tor01 on system infosec it create below files owned by coopnonprod-tor01

coopnonprod-tor01@infosec:/tmp$ ls -lart
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 836 Jul 5 16:42 sysdig-agent-clusterrole.yaml
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 3107 Jul 5 16:42 sysdig-agent-daemonset-v2.yaml
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 1282 Jul 5 16:42 sysdig-agent-configmap.yaml

Now from same system infosec I want to install sysdig agent from say different user coopnonprod-mon01 to different cluster,it just fails

coopnonprod-mon01@infosec:~/sysdig$ ./sysdig-install-agent-k8.sh -a 32d84351-a7e7-46xxxxxxx -c ingest.us-south.monitoring.cloud.ibm.com -ac 'sysdig_capture_enabled: true'

• Detecting operating system
• Downloading Sysdig cluster role yaml ---No errors and stops here
  coopnonprod-mon01@infosec:~/sysdig$

Looks like after install need to clean up files /tmp/sysdig-agent* which are owned by previous user.

Inizia con sysdig-install-agent-k8.sh e analizza come crea i file /tmp/sysdig-agent-clusterrole.yaml, /tmp/sysdig-agent-daemonset-v2.yaml e /tmp/sysdig-agent-configmap.yaml. Riproduci l’installazione con due utenti e verifica che un secondo utente possa installare correttamente dopo la prima installazione, senza file residui che lo blocchino.