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.

Sign up for GitHub

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

Jump to bottom

Come up with a better way to handle interrupted connections #52

Open
Cryptophobia opened this issue Mar 20, 2018 · 0 comments
Open

Come up with a better way to handle interrupted connections #52

Cryptophobia opened this issue Mar 20, 2018 · 0 comments

Comments

@Cryptophobia
Copy link
Member

From @helgi on September 15, 2016 22:52

Most of the time Deployments continue when HTTP connection is severed between our CLI and our API. However, if bad config/image etc is pushed then we are not in as nice of a spot. Things like DB records and so on are not cleaned up and you end up in with an "In Progress" Deployment (see below for one possible solution)

Deployments have a few things on the Kubernetes roadmap (https://github.com/kubernetes/community/wiki/Roadmap:-Deployment) but there is nothing we can depend on in the near term

See deis/controller#1071 for more context

Copied from original issue: deis/controller#1074
@Cryptophobia Cryptophobia mentioned this issue Mar 20, 2018
Open
duanhongyi added a commit to duanhongyi/controller that referenced this issue Nov 26, 2021
@duanhongyi
Merge pull request teamhephy#52 from jianxiaoguo/main
542481e 
chore(test): pretty pods list print
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Cryptophobia