docs(design): improve orchestrator deployment experience #290
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charlesmcchan
added
the
Proposal
charlesmcchan
requested review from
se-chris-thach,
mdbalvin,
rad-szulim,
yi-tseng-intel,
ashridatta,
teone,
callumnobleintel,
daniele-moro,
SeanCondon,
pierventre,
cgoea,
emmakenny,
PalashGoelIntel,
palade,
pperycz,
ltalarcz,
jakubsikorski,
sys-orch-approve,
ahalimx86,
johnoloughlin and
garyloug
as code owners
charlesmcchan
changed the title
charlesmcchan
changed the title
pierventre
reviewed
May 8, 2025
| - Every module should be **toggled independently** and have minimal external dependency. | ||
| - Installer should support **orchestrator CLI integration** (e.g. `cli deploy aws`) and parallel execution of non-dependent tasks. | ||
| - On-prem installation will not require a separate admin machine. | ||
| - Be compatible with upcoming Azure implementation and ongoing replacement of kind with on-prem in Coder |
There was a problem hiding this comment.
:(. Uff I was hoping for kind
There was a problem hiding this comment.
There are several benefits of focusing on the same deployment method that customers use.
We acknowledge that on-prem infra is not as lightweight as it can be, and we are committed to proposing and implementing a weight-loss program.
pierventre
reviewed
May 8, 2025
|
|
||
| ### Out of scope | ||
|
|
||
| - Optimizing total deployment time, as current durations are acceptable. |
There was a problem hiding this comment.
I belileve we have to discuss if there is any optimization possible here
pierventre
approved these changes
May 9, 2025
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This proposal aims to significantly improve the deployment experience of EMF across multiple environments (AWS, Azure, and on-prem).
The new installer will prioritize user experience by offering a streamlined, zero-touch installation process after configuration,
along with clear error handling and actionable feedback.
It will also increase cloud portability through clear infrastructure abstraction and support for Azure.
Finally, by replacing monolithic shell scripts with modular Go components and adding test coverage, we will enable faster iteration and more frequent releases.
Any Newly Introduced Dependencies
N/A
How Has This Been Tested?
N/A
Checklist: