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

adding dev instructions #100

Merged
merged 3 commits into from
Dec 13, 2021
Merged

adding dev instructions #100

merged 3 commits into from
Dec 13, 2021

Conversation

dgkanatsios
Copy link
Collaborator

Signed-off-by: Dimitris Gkanatsios dgkanatsios@outlook.com

Adding some instructions on how to run a custom thundernetes build on your Kubernetes cluster.

Signed-off-by: Dimitris Gkanatsios <dgkanatsios@outlook.com>
@dgkanatsios dgkanatsios added the area/build-tools Dev tooling that is in the build directory label Dec 6, 2021
@dgkanatsios dgkanatsios marked this pull request as draft December 6, 2021 09:16
@dgkanatsios dgkanatsios marked this pull request as ready for review December 6, 2021 19:22
Copy link
Collaborator

@khaines khaines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one suggestion, not blocking. Rest LGTM

To test your changes to thundernetes to a Kubernetes cluster, you can use the following steps:

- Go to the Makefile on the root of the project and change the container registry url to the one you have access to. It is stored in the variable `NS`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: change the NS varialbe in the Makefile to be a default, so that it can be overwritten via command args, ex: make NS=my-docker-repo.io (vs having to make a code change)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-tools Dev tooling that is in the build directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants