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

Add docs for perma-failed deployments #1337

Closed
wants to merge 1 commit into from
Closed

Add docs for perma-failed deployments #1337

wants to merge 1 commit into from

Conversation

0xmichalis
Copy link
Contributor

@0xmichalis 0xmichalis commented Sep 28, 2016

@kubernetes/deployment @erictune @smarterclayton


This change is Reviewable

@0xmichalis
Copy link
Contributor Author

Docs for kubernetes/kubernetes#19343

it. Once a Deployment times out, a related timeout Condition will be added in the status of the Deployment. Note that
if the error is transient eg. you have specified a low timeout or you don't have enough quota and all you need is to
scale down your Deployment or scale down other Pods you may be running then once the deployment controller notices
that your Deployment is complete, it will transition the failure condition into a succeeded one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need a sentence here about what being "failed" means (i.e. if the platform does anything beyond adding the condition, say that, otherwise say that Kube does nothing else). You should also include the example of how the JSON would look, and how kubectl get would look so someone could understand just by looking what this condition looks like.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -451,7 +451,79 @@ nginx-deployment-2035384211 0 0 1h
nginx-deployment-3066724191 0 0 1h
```

Note: A paused Deployment cannot be scaled at this moment, and we will add this feature in 1.3 release, see [issue #20853](https://github.com/kubernetes/kubernetes/issues/20853). You cannot rollback a paused Deployment either, and you should resume a Deployment first before doing a rollback.
Note: You cannot rollback a paused Deployment. You should resume it first before doing a rollback.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you create a separate PR for this? This change can go live now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened #1343

@janetkuo
Copy link
Member

Note that since perma-failed deployment isn't merged/released yet, this should either target 1.5 release branch (not yet created) or be added to 1.5 milestone (not yet created) and hold merging until 1.5.

@janetkuo janetkuo added component/deployment do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. labels Sep 28, 2016
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this pull request Oct 28, 2016
Automatic merge from submit-queue

Add perma-failed deployments API

@kubernetes/deployment @smarterclayton 

API for #14519

Docs at kubernetes/website#1337
@janetkuo
Copy link
Member

janetkuo commented Oct 28, 2016

Note: this depends on kubernetes/kubernetes#19343 (merged) and kubernetes/kubernetes#35691

k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this pull request Nov 4, 2016
…failed

Automatic merge from submit-queue

Controller changes for perma failed deployments

This PR adds support for reporting failed deployments based on a timeout
parameter defined in the spec. If there is no progress for the amount
of time defined as progressDeadlineSeconds then the deployment will be
marked as failed by a Progressing condition with a ProgressDeadlineExceeded
reason.

Follow-up to #19343

Docs at kubernetes/website#1337

Fixes #14519

@kubernetes/deployment @smarterclayton
@0xmichalis
Copy link
Contributor Author

Note: this depends on kubernetes/kubernetes#19343 (merged) and kubernetes/kubernetes#35691

Also kubernetes/kubernetes#36171 for the cli changes. All three of them are now merged.

@janetkuo
Copy link
Member

@Kargakis not sure if you saw @jaredbhatti's mail regarding docs targeting 1.5 features. Would you open another PR for this change, targeting 1.5 branch (instead of master), and assign or cc me there?

@janetkuo janetkuo added this to the 1.5 milestone Nov 15, 2016
@janetkuo
Copy link
Member

Ref feature issue kubernetes/enhancements#122

@janetkuo janetkuo removed the do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. label Nov 16, 2016
@0xmichalis
Copy link
Contributor Author

Opened #1699

@0xmichalis 0xmichalis closed this Nov 16, 2016
mikutas pushed a commit to mikutas/k8s-website that referenced this pull request Sep 22, 2022
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6)

---
updated-dependencies:
- dependency-name: minimist
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
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

Successfully merging this pull request may close these issues.

4 participants