Summary
We would like to submit a request to create a plugin repository under the argoproj-labs organization for the associated plugin. The plugin name could be of your choice, however if you need a name, we can call it rollouts-plugin-step-pagerduty as it will be a step plugin.
It will send PagerDuty events directly from Argo Rollouts when a canary deployment starts, succeeds, or fails.
Each event includes the rollout name, namespace, current phase, step index, and any custom details to configure. On failure the abort reason from Argo Rollouts is included in the alert payload. This will hopefully assist the user whom then has to be responsible to the alert/incident in which it is tied to.
Use Cases
- When a rollout fails, the plugin can send an alert to create an incident in the PagerDuty platform
- When a rollout starts, the plugin can send a change event to the PagerDuty platform
- When a rollout completes, the plugin can send a change event to the PagerDuty platform indicating the rollout being a sucess
Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.
Summary
We would like to submit a request to create a plugin repository under the argoproj-labs organization for the associated plugin. The plugin name could be of your choice, however if you need a name, we can call it
rollouts-plugin-step-pagerdutyas it will be a step plugin.It will send PagerDuty events directly from Argo Rollouts when a canary deployment starts, succeeds, or fails.
Each event includes the rollout name, namespace, current phase, step index, and any custom details to configure. On failure the abort reason from Argo Rollouts is included in the alert payload. This will hopefully assist the user whom then has to be responsible to the alert/incident in which it is tied to.
Use Cases
Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.