-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
Write Service Status Life Cycle test - +4 endpoint coverage #98018
Write Service Status Life Cycle test - +4 endpoint coverage #98018
Conversation
/triage accepted |
/assign @smarterclayton |
/retest |
6bae402
to
cdacda8
Compare
/test all |
/test pull-kubernetes-e2e-ubuntu-gce-network-policies
|
/test pull-kubernetes-e2e-ubuntu-gce-network-policies
|
/test all |
cdacda8
to
c00e1c0
Compare
/test all |
1 similar comment
/test all |
8e227bf
to
2f9840c
Compare
2f9840c
to
0993b7b
Compare
/test pull-kubernetes-e2e-kind
|
@johnbelamaric all the comments have been addressed. please take a look. Do you want any other sig-network approvers to chime in too? |
@heyste have updated the |
0993b7b
to
13708ce
Compare
I don't want to block on this comment, just want to open a discussion based on this e2e test approach for following up later. I'm far from an expert on the area, but I always see that the recommendation is to not use watchers directly because they are not able to handle disconnects, most of the e2e use the @BenTheElder @wojtek-t @liggitt what do you think? I think that it will be useful to set some guidelines on the e2e tests so we have some consistency on the code. |
e2e test validates the following service status endpoints - patchCoreV1NamespacedServiceStatus - readCoreV1NamespacedServiceStatus - replaceCoreV1NamespacedServiceStatus Also includes untested service endpoint - patchCoreV1NamespacedService
13708ce
to
3e9c44f
Compare
Ingress: []v1.LoadBalancerIngress{{IP: "203.0.113.1"}}, | ||
} | ||
lbStatusJSON, err := json.Marshal(lbStatus) | ||
framework.ExpectNoError(err, "Failed to marshal JSON. %v", err) |
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.
this looks funny :) err
twice
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.
just a nit. no need to fix right now
/approve let's please iterate if needed. we need to get this to soak quickly |
/lgtm @aojea we have built some defenses in for watch failures, we do want to use watch in a number of these tests. in this one in particular, we need to use watch otherwise we may miss our update due to fighting with the controller that is actually managing the resource. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, johnbelamaric, Riaankl 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 |
👍 cool, nice to know |
/test pull-kubernetes-e2e-kind Unrelated flake
|
/test pull-kubernetes-integration Unrelated flake
|
@Riaankl: The following test 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/test-infra repository. I understand the commands that are listed here. |
/test pull-kubernetes-e2e-kind
|
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR adds a test to test the following untested endpoints:
Which issue(s) this PR fixes:
Fixes #94867
Testgrid Link:
Link
Special notes for your reviewer:
Adds +4 endpoint test coverage (good for conformance)
Does this PR introduce a user-facing change?:
Release note:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig testing
/sig architecture
/area conformance