Progressive Delivery #93
chris-short
started this conversation in
General
Replies: 3 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
-
|
AWS architecture is massive and from what I know this article is still accurate and could be a guiding example for large deployments. |
Beta Was this translation helpful? Give feedback.
-
|
I've seen folks doing multiple branches that split up the prod environment to a manageable blue/green. Some the branch name would be (as an example): product v.X.Y.Z-wave-1, 2, 3, and so on. That's certainly a valid GitOps pattern if it's automated, in my opinion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'd like to start a discussion around this topic to get a better idea of what people are seeing/doing around progressive delivery (or minimizing blast radius of improper configurations).
There are a number of progressive delivery tools out there. Some work really well with existing GitOps controllers. I think it would make sense for us to pull together a best practices doc or guide around this subject. We can highlight tools but, we shouldn't say one tool is the de facto tool because we shouldn't be THAT opinionated.
I'd love to hear more around what folks are doing in this space and would like to work with other contributors on establishing some documentation on this topic.
Beta Was this translation helpful? Give feedback.
All reactions