-
Notifications
You must be signed in to change notification settings - Fork 100
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
updating doc to use DE from existing installation #7964
base: main
Are you sure you want to change the base?
Conversation
.vscode/launch.json
Outdated
"KUBERNETESBICEPEXTENSIBILITYURL": "http://localhost:5017/api", | ||
"RADIUSBACKENDURI": "http://localhost:9000", | ||
}, | ||
}, |
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.
Can we leave this here? It's still useful.
That gives users the choice of either:
- Using the DE from a cluster
- Using the DE from local source code
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7964 +/- ##
=======================================
Coverage 59.83% 59.83%
=======================================
Files 590 590
Lines 39520 39520
=======================================
Hits 23646 23646
Misses 14119 14119
Partials 1755 1755 ☔ View full report in Codecov by Sentry. |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
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 updating this @nithyatsu. Were you able validate that this setup works?
...ntributing/contributing-code/contributing-code-control-plane/running-controlplane-locally.md
Outdated
Show resolved
Hide resolved
...ntributing/contributing-code/contributing-code-control-plane/running-controlplane-locally.md
Outdated
Show resolved
Hide resolved
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
6. (Optional) Configure any cloud provider credentials you want to use for developing Radius. | ||
1. Create a Kubernetes cluster, or set your current context to a cluster you want to use. The debug configuration will use your current cluster for storing data. | ||
2. If you have access to `radius-project/deployment-engine` repo, | ||
1. Clone the `radius-project/radius` and `radius-project/deployment-engine` repo next to each other. |
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.
1. Clone the `radius-project/radius` and `radius-project/deployment-engine` repo next to each other. | |
1. Clone the `radius-project/radius` and `radius-project/deployment-engine` repos next to each other. |
"Launch Applications RP", | ||
"Launch Dynamic RP", | ||
"Launch Controller", | ||
// "Launch Deployment Engine" |
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.
This is only if we are running Deployment Engine as a container, right? Should we specify that or delete this line all together?
5. Install C# VS Code extension - <https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp>. | ||
6. (Optional) Configure any cloud provider credentials you want to use for developing Radius. | ||
1. Create a Kubernetes cluster, or set your current context to a cluster you want to use. The debug configuration will use your current cluster for storing data. | ||
2. If you have access to `radius-project/deployment-engine` repo, |
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.
Can write down this and Setup Step 4: Run Deployment Engine as docker container
as either/or? Even if someone has access, they don't need to clone it and can directly run DE in a container?
"Launch Applications RP", | ||
"Launch Dynamic RP", | ||
"Launch Controller", | ||
// "Launch Deployment Engine" |
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.
This can be a bit confusing, let's separate out the two paths with clearer instructions. You either clone the repo or spin it up in container and call out any updates required to launch config in each scenario.
- Press Debug | ||
|
||
Wait for all 3 of these to start. | ||
Wait for all the services to start. |
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 updating this.
|
||
> 💡 This step is required only if you are an external contributor and do not have access to `radius-project/deployment-engine` repo. | ||
> | ||
`docker run -e RADIUSBACKENDURL=http://host.docker.internal:9000/apis/api.ucp.dev/v1alpha3 -p 5017:8080 ghcr.io/radius-project/deployment-engine:latest` |
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.
Are there any prerequisites to running this command that we should mention here?
Description
deployment-engine is currently a private repo. Updating contributor docs to use DE from existing installation.
Type of change