-
Notifications
You must be signed in to change notification settings - Fork 468
Documentation on how to setup the Build-VM (via chef on GCP) to Development.md #2191
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
base: main
Are you sure you want to change the base?
Conversation
Starting docu of vm setup on gcp with terraform and chef Signed-off-by: entlein <einentlein@gmail.com>
From mobile phone Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
…if desired Signed-off-by: entlein <einentlein@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this together @entlein! Setting up our development environment has always come with a steep learning curve due to some undocumented aspects, but these updates will definitely make the process much smoother!
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
…language Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
…n manual install, needs to be tested, do NOT MERGE Signed-off-by: entlein <einentlein@gmail.com>
…optional Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
…optional Signed-off-by: entlein <einentlein@gmail.com>
Co-authored-by: Dom Delnano <ddelnano@gmail.com> Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Co-authored-by: Dom Delnano <ddelnano@gmail.com> Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Co-authored-by: Dom Delnano <ddelnano@gmail.com> Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
linter Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
linter Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two more minor comments and then this is good to go.
best typo ever Co-authored-by: Dom Delnano <ddelnano@gmail.com> Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Signed-off-by: entlein <einentlein@gmail.com>
Summary: Documentation on how to setup the Build-VM (via chef on GCP) to Development.md
On our GCP setup, we documented how to configure a VM as remote workstation to run Pixie on minikube using our registry. We wrote down the commands and hope others may find them useful.
Relevant Issues: N/A
Avoid having to bother the maintainers with questions about setting up development.
Type of change: /kind documentation
Test Plan: Tested this through the following
The tests were conducted manually on GCP by using a terraform code to create the VM/Network/Rules etc and then by manually logging in and running the commands exactly in the order given in Development.md
This could be done fully automated (via TF, ansible, chef), up to the point where px auth login requires interactivity.
Changelog Message: Added documentation for getting started with Pixie development via a development VM