Canary Release Support
complete
J
Jason Griffin
Provide automation for progressive delivery using traffic shaping.
Validation of a release would be based on a set of one or more user specified SLOs
Validation would target one or more segments (group of users with shared characteristics such as geolocation, browser UA, cookie)
The target segment or segments are specified by the user
The API requests for the target segment are automatically routed to the new version (traffic shaping) all other requests go the current "live" version
The failure to meet any one of the defined SLOs would cause the release to be immediately rolled back
Rollbacks automatically revert all API requests to the "live" version and optionally could trigger a CCI pipeline and/or call a user specified webhook or webhooks
If the release meets all the specified SLO then all requests are routed to the new version and the new version becomes the "live" version
Alexa Zeazas Loper
complete
Our Release Agent is in open preview and integrates with Argo Rollouts, which supports analysis runs via many of the common observability tools. https://circleci.com/docs/release/releases-overview/
A
Adam Wilhelm
It would be amazing if we could use external metrics for verification of canary deployments. This would include external systems like Datadog or Coralogix.
J
Jason Griffin
in progress