code review

Makefile

@@ -115,6 +115,8 @@ manifests: controller-gen ## Generate manifests e.g. CRD, RBAC etc.
 
 # Run e2e tests locally using go build while also setting up a proxy in the shell to allow
 # the test to run as if it were inside the cluster. This enables mongodb connectivity while running locally.
+# "MDB_LOCAL_OPERATOR=true" ensures the operator pod is not spun up while running the e2e test - since you're
+# running it locally.
 e2e-telepresence: cleanup-e2e install ## Run e2e tests locally using go build while also setting up a proxy e.g. make e2e-telepresence test=replica_set cleanup=true
 	export MDB_LOCAL_OPERATOR=true; \
 	telepresence connect; \

docs/run-operator-locally.md

@@ -12,7 +12,7 @@ Being able to run and build the binary locally can help with faster feedback-cyc
     - `KUBECONFIG` environment variable pointing at a file
     - **Note**: either of these are necessary to be able to run the operator locally
 - Have a folder `.community-operator-dev`
-- *Optional - if you want to export the environment variables, you can run the following command*: `source .community-operator-dev/local-test.export.env`
+- *Optional - if you want to export the environment variables, you can run the following command*: `source .community-operator-dev/local-test.export.env`. ( These environment variables are generated with the `make generate-env-file`)
 ## Goals
 - Run the operator locally as a binary (optionally in debug mode) in command line or in an IDE
 - Run e2e tests locally