Initial attempt at addressing the NEBARI_KUBECONFIG in tmp issue rais…

…ed in #83 and #88. May need some more detail.

docs/docs/troubleshooting.md

@@ -6,6 +6,7 @@ Invariably you will encounter behavior that does not match your expectations. Th
 
  - DNS domain=1your_nebari_domain1 record does not exist
  - User instances on AWS occasionally die ~30 minutes after spinning up a large dask cluster
+ - Why is the `NEBARI_KUBECONFIG` file in `/tmp`?
 
 [_Errors_](#errors)
 
@@ -39,6 +40,10 @@ AWS uses Elastic Kubernetes Service for hosting the Kubernetes cluster. [It requ
 
 To stop this from happening, the autoscaler service "AZRebalance" needs to be manually suspended. You can [follow the steps in the AWS documentation to suspend the AZRebalance service](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html).
 
+### Why is the `NEBARI_KUBECONFIG` file in `/tmp`?
+
+Nebari regenerates this file on every run. Yes, it will be trashed by the operating system's tmpdir cleanup, but it will be repopulated.
+
 ## Errors
 
 ### Conda-Store environment fails to build