-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Adds daemonset conformance tests #60456
Conversation
test/e2e/apps/daemon_set.go
Outdated
@@ -108,7 +108,12 @@ var _ = SIGDescribe("Daemon set [Serial]", func() { | |||
Expect(err).NotTo(HaveOccurred()) | |||
}) | |||
|
|||
It("should run and stop simple daemon", func() { | |||
/* | |||
Testname: Simple DaemonSet Creation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if it matters, but the example and all existing Testnames in the repo have no spaces.
https://github.com/kubernetes/kubernetes/blob/master/test/conformance/cf_header.md
test/e2e/apps/daemon_set.go
Outdated
@@ -175,6 +185,8 @@ var _ = SIGDescribe("Daemon set [Serial]", func() { | |||
Expect(err).NotTo(HaveOccurred()) | |||
}) | |||
|
|||
// We deffer adding this test to conformance pending the disposition of moving DaemonSet scheduling logic to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: defer
7278ddd
to
76a9656
Compare
test/e2e/apps/daemon_set.go
Outdated
/* | ||
Testname: DaemonSet-Creation | ||
Description: A conformant Kubernetes distribution MUST support the creation of DaemonSets. When a DaemonSet | ||
Pod is deleted, the DaemonSet controller MUST recreate the Pod. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we never "recreate" a Pod but simply create a new one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
making the distinction makes sense to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this terminology is ok in this case because the pod is associated with the node. The terminology I generally discourage is "reschedule".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll go with Janet's suggestion because its conformance and someone might infer that we are updating the Pod in place. In general I wouldn't read "recreate" as in place update, but it can't hurt.
76a9656
to
4ec6853
Compare
test/e2e/apps/daemon_set.go
Outdated
It("should retry creating failed daemon pods", func() { | ||
/* | ||
Testname: DaemonSet-FailedPodRecreation | ||
Description: A conformant Kubernetes distribution MUST recreate DaemonSet Pods when they fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment here for "recreate" (L238 - L239)
test/e2e/apps/daemon_set.go
Outdated
@@ -223,7 +235,11 @@ var _ = SIGDescribe("Daemon set [Serial]", func() { | |||
NotTo(HaveOccurred(), "error waiting for daemon pod to not be running on nodes") | |||
}) | |||
|
|||
It("should retry creating failed daemon pods", func() { | |||
/* | |||
Testname: DaemonSet-FailedPodRecreation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testname: DaemonSet-FailedPodCreation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or "Testname: DaemonSet-FailedPodRetryCreation"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this one reads oddly. It sounds like the Pod is not having fun. :-)
3ac3d8f
to
afedbf9
Compare
/approve |
I believe all prior comments are now addressed. /lgtm |
test/e2e/apps/daemon_set.go: "should run and stop complex daemon" | ||
test/e2e/apps/daemon_set.go: "should retry creating failed daemon pods" | ||
test/e2e/apps/daemon_set.go: "Should update pod when spec was updated and update strategy is RollingUpdate" | ||
test/e2e/apps/daemon_set.go: "Should rollback without unnecessary restarts" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not capitalize "Should" to make it consistent with other tests?
/restest |
/retest |
afedbf9
to
1f16519
Compare
1f16519
to
dcc3d25
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgrant0607, janetkuo, kow3ns The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Automatic merge from submit-queue (batch tested with PRs 52077, 60456, 60591). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it: Adds conformance tests for deamonset