replace tilt with radius for k8s deployment #301
Draft
+19
−116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the Kubernetes deployment instructions for TraderX to use Radius instead of Tilt.dev, streamlining the setup for both local and cloud environments. The changes remove documentation and configuration related to Tilt.dev and improve clarity and guidance for deploying with Radius.
Deploying with Radius has the following advantages:
Documentation and Deployment Workflow Update:
README.md
to replace Tilt.dev instructions with steps for deploying TraderX using Radius, including prerequisites, deployment commands, and cleanup instructions. This provides a more modern and production-like workflow for local and cloud deployments.radius-traderx/README.md
, which previously contained separate Radius deployment instructions, consolidating all guidance into the mainREADME.md
.Configuration Cleanup:
workspace
configuration fromradius-traderx/.rad/rad.yaml
, as it is no longer relevant with the updated Radius workflow.