Add deployment chain RFC #2743
Add deployment chain RFC #2743
Conversation
|
Code coverage for golang is |
|
Still reading the RFC but just left some quick reviews. |
|
Code coverage for golang is |
|
Code coverage for golang is |
|
It would be nice if you can add a screenshot of a simple mock page of the "Flows" or "Chains" tab. |
|
Code coverage for golang is |
|
Thanks @nghialv @nakabonne, PTAL when you guys have time 🙆♀️ |
|
Code coverage for golang is |
|
Code coverage for golang is |
Co-authored-by: Le Van Nghia <nghialv2607@gmail.com>
Co-authored-by: Le Van Nghia <nghialv2607@gmail.com>
|
Code coverage for golang is |
…o add-deployment-flow-rfc
|
Code coverage for golang is |
| Use-case <1>: chain of deployments contains multiple application cross kinds | ||
|
|
||
| Another typical use-case is when users want to build up some kind of chain such as deploy application to the development environment, then if it's done successfully, deploy that application to the staging and then the production environment. | ||
|
|
There was a problem hiding this comment.
How about following the layout below to be easier to read?
Use-case <1> ...
Image 1
Description text for use-case 1
Use-case <2> ...
Image 2
Description text for use-case 2
Use-case <3> ...
Image 3
Description text for use-case 3
|
|
||
| Or a variant of that requirement, when users want to roll out their applications to their cluster one by one based on its region. As the same below image, the order of the rolling out deployment should be flex, supports both sequential and parallel. | ||
|
|
||
|  |
There was a problem hiding this comment.
All the application names in this image should be fixed as application-x-region-a, application-x-region-b, ...
Co-authored-by: Le Van Nghia <nghialv2607@gmail.com>
|
Code coverage for golang is |
|
Code coverage for golang is |
|
Code coverage for golang is |
|
Finally, we can see a nice future for the deployment chain feature. |
|
I'm sure this will blow their mind! |
|
This pull request is APPROVED by Approvers can cancel the approval by writing |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: