-
Notifications
You must be signed in to change notification settings - Fork 170
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
Add run-rp docs #3819
base: master
Are you sure you want to change the base?
Add run-rp docs #3819
Conversation
- adds documentation on build/run dependencies of containerized build - adds instructions on how to use 'make run-rp'
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Perhaps the containerized mode could use either its own page or its own sessions on how setup it, with a shorter set of commands that is required only to succeed make run-rp
.
Option 2: using containerized build and run (requires local `podman` and `openvpn`): | ||
```bash | ||
# establish a VPN connection to the shared dev environment Hive cluster | ||
sudo openvpn secrets/vpn-${LOCATION}.ovpn & |
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.
From my testing it must be vpn-aks-$LOCATION.ovpn
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.
There should be variations of both secrets/vpn-${LOCATION}.ovpn
and secrets/vpn-aks-${LOCATION}.ovpn
for every dev region. I've always used the non-aks one locally 🤔 and have tested this in westeurope
with success... do we have diverging dev environments maybe?
Which issue this PR addresses:
Follow up to split between
runlocal-rp
andrun-rp
- these docs outline how to use the new feature of containerized builds and RP executionWhat this PR does / why we need it:
Docs
Test plan for issue:
N/A - docs
Is there any documentation that needs to be updated for this PR?
Yes, this PR
How do you know this will function as expected in production?
N/A - docs