-
Notifications
You must be signed in to change notification settings - Fork 40.2k
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
Promote resourceQuota e2e verifying 'object count quota' and 'quota scope' to Conformance #78331
Promote resourceQuota e2e verifying 'object count quota' and 'quota scope' to Conformance #78331
Conversation
/test pull-kubernetes-integration |
/assign @yliaog |
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.
very minor comment, but I didn't see anything in the tests that I think should be disqualifying.
When you make the update, I'll dig in deeper.
6ff2fb2
to
2b15e34
Compare
@@ -22,7 +22,7 @@ import ( | |||
"time" | |||
|
|||
appsv1 "k8s.io/api/apps/v1" | |||
"k8s.io/api/core/v1" | |||
v1 "k8s.io/api/core/v1" |
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.
Note for reviewer: I suspect, recent gofmt
or goimport
adding this named import alias.
/test pull-kubernetes-bazel-build |
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
I still need to go through the tests in detail but moving columns in case others have more time than me to approve.
2b15e34
to
2c6fbc1
Compare
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a configMap." | ||
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a replication controller." | ||
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a replica set." | ||
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a persistent volume claim." |
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.
Please remove the PV and PVC tests. They aren't ready for conformance yet. We don't have any PV or PVC tests yet.
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.
Removed.
Create a ConfigMap. Its creation MUST be successful and resource usage count against the ConfigMap object MUST be captured in ResourceQuotaStatus of the ResourceQuota. | ||
Delete the ConfigMap. Deletion MUST succeed and resource usage count against the ConfigMap object MUST be released from ResourceQuotaStatus of the ResourceQuota. | ||
*/ | ||
framework.ConformanceIt("should create a ResourceQuota and capture the life of a configMap.", func() { |
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.
Does this test really need to be so complicated, or did it just copy the secret test?
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.
@mikedanese asked a similar question when this test was first introduced https://github.com/kubernetes/kubernetes/pull/68812/files#r230931734
Per comments below this is making an allowance for ca.crt
to show up
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.
Why do we need to do that? Is this just related to how we have configured the e2e cluster? If there is this race condition in pod startup, it would seem that users can hit this too, we shouldn't just work around it.
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 agree with removing the PV/PVC tests but otherwise feel like clarifying comments and such are scope creep.
Description: Create a ResourceQuota. Creation MUST be successful and its ResourceQuotaStatus MUST match to expected used and total allowed resource quota count within namespace. | ||
Create a Secret. Its creation MUST be successful and resource usage count against the Secret object and resourceQuota object MUST be captured in ResourceQuotaStatus of the ResourceQuota. | ||
Delete the Secret. Deletion MUST succeed and resource usage count against the Secret object MUST be released from ResourceQuotaStatus of the ResourceQuota. | ||
*/ |
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.
It would be nice but I wouldn't block promoting on the lack of such a comment. The test has been like this for a while.
On contended servers the service account controller can slow down,
leading to the count changing during a run. Wait up to 5s for the count
to stabilize, assuming that updates come at a consistent rate, and are
not held indefinitely.
Create a ConfigMap. Its creation MUST be successful and resource usage count against the ConfigMap object MUST be captured in ResourceQuotaStatus of the ResourceQuota. | ||
Delete the ConfigMap. Deletion MUST succeed and resource usage count against the ConfigMap object MUST be released from ResourceQuotaStatus of the ResourceQuota. | ||
*/ | ||
framework.ConformanceIt("should create a ResourceQuota and capture the life of a configMap.", func() { |
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.
@mikedanese asked a similar question when this test was first introduced https://github.com/kubernetes/kubernetes/pull/68812/files#r230931734
Per comments below this is making an allowance for ca.crt
to show up
/lgtm cancel |
/remove-kind api-change |
…cope' to Conformance
bdd82e2
to
a921970
Compare
/retest |
/lgtm |
There are not any big changes which seem related to flake in this year at least since f58c2ae (There is a lot of cleanup changes btw) /lgtm |
/assign @bgrant0607 @smarterclayton |
/approve Quota is fundamental to a Kube system |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mgdevstack, smarterclayton 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 |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Promoting following e2e to Conformance -
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and ensure its status is promptly calculated."
Execution time: 13.192 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a service."
Execution time: 17.307 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a secret."
Execution time: 23.227 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a pod."
Execution time: 19.307 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a configMap."
Execution time: 22.230 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a replication controller."
Execution time: 17.307 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a replica set."
Execution time: 17.235 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a persistent volume claim."
Execution time: 17.231 seconds
test/e2e/apimachinery/resource_quota.go: "should create a ResourceQuota and capture the life of a persistent volume claim with a storage class."
Execution time: 17.243 seconds
test/e2e/apimachinery/resource_quota.go: "should verify ResourceQuota with terminating scopes."
Execution time: 22.325 seconds
test/e2e/apimachinery/resource_quota.go: "should verify ResourceQuota with best effort scope."
Execution time: 22.333 seconds
test/e2e/apimachinery/resource_quota.go: "Should be able to update and delete ResourceQuota."
Execution time: 6.206 seconds
Which issue(s) this PR fixes:
Fixes #78831
Special notes for your reviewer:
[Feature:ScopeSelectors]
labelled here and[Feature:PodPriority]
labelled here?kind
cluster.Does this PR introduce a user-facing change?:
/area conformance
/area testing
@kubernetes/sig-api-machinery-pr-reviews
@kubernetes/sig-architecture-pr-reviews
@kubernetes/cncf-conformance-wg