Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify deployments before serving traffic #2256

Open
theseanything opened this issue Aug 5, 2024 · 1 comment
Open

Verify deployments before serving traffic #2256

theseanything opened this issue Aug 5, 2024 · 1 comment

Comments

@theseanything
Copy link
Contributor

theseanything commented Aug 5, 2024

Currently, we promote a deployment to an environment (e.g. staging, production), which involves serving live traffic to the new version as soon as pods are available. Then post rollout, we then run the smokey tests to verify the deployment. If the smoke tests fail we send a notification, however do not rollback if there's a failure with the smoke tests. This is okay for integration or staging, as it prevents the automatic promotion of the deployment to production. However doesn't help stop issues, if the failures are only seen in production.

We could use progressive delivery (such as Argo Rollouts) to run verifications (smoke tests) on application before serving live traffic and allowing us to automatically rollback to the previous version.

@theseanything
Copy link
Contributor Author

As requests are proxied via router from Frontend apps, this makes it difficult to test the preview service. Could use header-based traffic management, however that would require a service mesh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant