Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update debugging.md #412

Merged
merged 1 commit into from
Sep 23, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/development/debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ To test your changes to Thundernetes on a Kubernetes cluster, you can use the fo
- The Makefile on the root of the project contains a variable `NS` that points to the container registry that you use during development. So you'd need to either set the variable in your environment (`export NS=<your-container-registry>`) or set it before calling `make` (like `NS=<your-container-registry> make build push`).
- Login to your container registry (`docker login`)
- Run `make clean build push` to build the container images and push them to your container registry
- Run `create-install-files-dev` to create the install files for the cluster
- Run `make create-install-files-dev` to create the install files for the cluster
- Checkout the `installfilesdev` folder for the generated install files. This file is included in .gitignore so it will never be committed.
- Test your changes as required. For example, to install Thundernetes controller, you can do `kubectl apply -f installfilesdev/operator_with_monitoring.yaml` and then you can install any of the samples on the `samples` folder.
- single command: `NS=docker.io/<repo>/ make clean build push create-install-files-dev`