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

Implement other definitions for success #3

Open
Mikulas opened this issue Apr 29, 2020 · 0 comments
Open

Implement other definitions for success #3

Mikulas opened this issue Apr 29, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@Mikulas
Copy link
Member

Mikulas commented Apr 29, 2020

Rollout status currently blocks until all requested pods are successfully started. This is intentional as we don't want to start QA and other parts of the CI/CD pipeline with parts with part of the traffic still being served from old pods. This should be added to documentation.

Furthermore, the rollout may fail for some pods (mounting volumes, resource constraints, …) even when a one pod is successful.

So far I don't see a use case for other modes, but I'm actively looking for them.

@Mikulas Mikulas added documentation Improvements or additions to documentation question Further information is requested labels Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant