-
Notifications
You must be signed in to change notification settings - Fork 40.9k
[WIP] add e2e tests for DeploymentPodReplacementPolicy #126176
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
base: master
Are you sure you want to change the base?
Conversation
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test ? |
@atiratree: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-kubernetes-e2e-storage-kind-alpha-features |
/test pull-kubernetes-e2e-kind-alpha-features |
85a8ace
to
df8a3e5
Compare
/test pull-kubernetes-e2e-kind-alpha-features |
/test pull-kubernetes-e2e-kind-alpha-beta-features |
/test pull-kubernetes-e2e-kind-alpha-features |
081230b
to
5fb32bc
Compare
78583c6
to
61d5871
Compare
61d5871
to
4728929
Compare
4728929
to
a39ed56
Compare
a39ed56
to
32268ec
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: atiratree The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
- add podReplacementPolicy field to Deployment's spec versioned API
Consider the TerminationStarted and TerminationComplete policies when rolling out a new deployment with a Recreate or RollingUpdate strategy. Also consider these policies when scaling any deployment, either during or after a rollout has been completed. Special care has to be taken when scaling up multiple replicasets proportionally. If a replicaset cannot be fully scaled, "deployment.kubernetes.io/replicaset-replicas-before-scale" annotation is added to the replicaset so that it can be scaled again in the future once the extra pods terminate.
terminate, before marking the deployment as complete
32268ec
to
d090679
Compare
@atiratree: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/test pull-kubernetes-node-e2e-containerd |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: