-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
LimitRange e2e test improved. #55065
Conversation
/ok-to-test
needs @kubernetes/sig-architecture-feature-requests (cc @timothysc) approval in a SIG meeting as well |
/retest |
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.
/lgtm but we need @kubernetes/sig-architecture-pr-reviews to approve any conformance changes
@kmrov please add a release note though to callout any conformance additions.
options := metav1.ListOptions{LabelSelector: selector.String()} | ||
limitRanges, err := f.ClientSet.CoreV1().LimitRanges(f.Namespace.Name).List(options) | ||
Expect(err).NotTo(HaveOccurred(), "failed to query for limitRanges") | ||
Expect(len(limitRanges.Items)).To(Equal(0)) |
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 would warn here b/c we've seen a number of test conditions fail on loaded clusters due to waiting on cleanup conditions. I realize that it shouldn't occur, but we've seen patterns of odd cleanup when running (N) overlapping test cases with namespaces names that are not completely unique.
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.
What can you suggest to do to avoid the problems here?
Expect(err).NotTo(HaveOccurred(), "failed to set up watch") | ||
|
||
By("Submitting a LimitRange") | ||
limitRange, err = f.ClientSet.CoreV1().LimitRanges(f.Namespace.Name).Create(limitRange) |
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.
Update vs. Create based on previous value of list.
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.
Should Update at line 140 use a new LimitRange structure, not the old with changed limit value?
We definitely need an associated issue here. Is there any tracking issue / doc for changes to the Conformance suite over time? |
@kmrov @timothysc |
Looks like the hold is for |
8f4f43d
to
41c20f4
Compare
Yes, the hold was due to the conformance tag. Since that was removed, I removed the hold. Thanks for the test improvements. |
/priority important-longterm |
/retest |
@timothysc LGTM this for real as the Conformance tag was removed? |
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.
/lgtm
/approve
@timothysc a comment |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kmrov, timothysc Associated issue requirement bypassed by: timothysc The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/status in-progress |
/priority critical-urgent /remove-priority important-longterm adjusting priorities for code freeze |
[MILESTONENOTIFIER] Milestone Pull Request Current Note: This pull request is marked as Example update:
Pull Request Labels
|
Automatic merge from submit-queue (batch tested with PRs 52767, 55065, 55148, 56228, 56221). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it: Improves the e2e test for LimitRange API by testing Update, Delete and Watch features.
Release note: