You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/run-operator-locally.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ Being able to run and build the binary locally can help with faster feedback-cyc
20
20
## Running The Operator locally
21
21
1. Use the dedicated make target which exports the needed environment variables and builds & runs the operator binary.
22
22
23
-
Before doing that you need to add 2 more fields to the `config.json` file from in [contributing.md](contributing.md):
24
-
-`mdb_local_operator`: needs to be set to `true`
25
-
-`kubeconfig`: needs to be set to the path of the configuration file mentioned above
23
+
Before doing that you need to add 2 more fields to the `config.json` file found in [contributing.md](contributing.md), because the python script looks for them in the file:
24
+
-`mdb_local_operator`: needs to be set to `true`, to allow for the operator to be run locally
25
+
-`kubeconfig`: needs to be set to the path of the `kubeconfig`configuration file, for example `$HOME/.kube/config`
0 commit comments