You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was wondering if there was already any reasoning ongoing for supporting canary releases, for example relying on EXTERNAL deployments. Here some references on the topic:
external deployments, see here and here. additional resources here and here
example with Jenkins as the external tool for orchestrating, see here and here
Ok, so I just started prototyping this, and indeed it was not so complex to arrange a skeleton version with proper canary and stable deployments, controlled by the script. For reference, I'm working here.
@fillup just created a WIP PR for this, in order to get some feedback on the overall idea!
I'm currently using on development, not yet on production envs, and so far feedback is good, even if it lacks some more robust error handling.
Hi, I was wondering if there was already any reasoning ongoing for supporting canary releases, for example relying on
EXTERNAL
deployments. Here some references on the topic:Briefly, should be a matter of migrating from task-definitions and force service deployments, to interact with task set and ELB listeners.
I'd like contributing, but don't want to overlap with any ongoing effort on the topic!
The text was updated successfully, but these errors were encountered: