This message was deleted.

You could mark the kubeconfig as a secret and it won't be dumped raw into the command line. Then refer to the kubeconfig from the meta stack using a stack reference. You could also do this through an automation api program instead where you run the

kubernetes stack

first, pull out the kubeconfig (still exported as an output) and then run the meta stack from the same program. With this you could just export the kubeconfig to a file and set KUBECONFIG env var before initiating the second stack (or use the stack reference trick above)

Thanks for responding Vivek! I implemented something similar. Thanks for the help