This message was deleted.

If you want a file then add

--dry-run=client --output=yaml

and pipe the output into a file

Why would you stick your admin kubeconfig into a Kubernetes secret, instead of just using a service account? If you need access to Kubernetes from within the cluster, that is literally what service accounts are for. Sticking your admin kubeconfig in there so you can use it in pods is definitely an anti-pattern.

I wanted a file as a reaction to running that command or some other way to manage that secret without recreating it every time. However, Brandon's clarity on using a service account is enough for me to push back on this. It didn't make sense (because I know 0 about argo), but now that I know it can be accomplished with an SA instead, I'm going to push for it. Thanks a ton for the help folks.