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

Automate releases with different deployment strategies & rollback plan #12

Closed
Clivern opened this issue Feb 13, 2020 · 0 comments
Closed

Comments

@Clivern
Copy link
Owner

Clivern commented Feb 13, 2020

Figure out how to do that. Also a way to get all releases available for deployment or text input/api parameter

Deployment strategies that can be supported.

recreate: terminate the old version and release the new one.
ramped: release a new version on a rolling update fashion, one after the other.
blue/green: release a new version alongside the old version then switch traffic.
canary: release a new version to a subset of users, then proceed to a full rollout.

Client -->
https://github.com/kubernetes/client-go/blob/master/kubernetes/typed/core/v1/core_client.go

@Clivern Clivern added the Type: Feature New feature or request label Feb 13, 2020
@Clivern Clivern added this to the 🚀 Badass v0.1.0 milestone Feb 13, 2020
@Clivern Clivern changed the title Find a way to automate releases with different deployment strategies & rollback Automate releases with different deployment strategies & rollback Feb 13, 2020
@Clivern Clivern changed the title Automate releases with different deployment strategies & rollback Automate releases with different deployment strategies & rollback plan Feb 13, 2020
@Clivern Clivern pinned this issue Feb 13, 2020
@Clivern Clivern unpinned this issue Feb 14, 2020
Clivern added a commit that referenced this issue Feb 15, 2020
Clivern added a commit that referenced this issue Mar 8, 2020
Clivern added a commit that referenced this issue Mar 8, 2020
Clivern added a commit that referenced this issue Mar 10, 2020
Clivern added a commit that referenced this issue Mar 10, 2020
@Clivern Clivern closed this as completed Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant