-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
use LoadBalancer type service for e2e service test to patch ingress status #119454
Conversation
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/test-infra repository. |
/priority important-soon |
/lgtm |
LGTM label has been added. Git tree hash: 317b55dc51fd032fd40c8255374daa7c29d57ba0
|
kubernetes/pkg/apis/core/validation/validation.go Lines 7066 to 7069 in 4457f85
Any advice? @thockin |
Either can solve the failure without the e2e test change. |
LGTM label has been added. Git tree hash: 6c480982b7afb633749f9fce9a31047050ba7ae0
|
/retest |
+1 for |
/approve heh, this is why everybody loves Service 🙃 what an interesting failure |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, pacoxu, thockin 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 |
/hold cancel only impacts an alpha feature gate |
/retest |
/checkcla |
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 the timeout at L3518 is now too short for an LB service.
We should either call GetServiceLoadBalancerPropagationTimeout or call e2eservice.WaitForServiceDeletedWithFinalizer or just bump this timeout or something.
Do we really need to test patch here? If not, it would be simpler to remove this section - it is exercised in the loadbalancer tests already.
/retest |
/retest-required |
/hold we need to understand the consequnces of using a LoadBalancer |
test/e2e/network/service.go
Outdated
@@ -3357,6 +3357,7 @@ var _ = common.SIGDescribe("Services", func() { | |||
Port: int32(80), | |||
TargetPort: intstr.FromInt(80), | |||
}}, | |||
LoadBalancerClass: utilpointer.String("test.com/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.
super super nit: example.com
should be used for things like this.
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.
Updated to "example.com/internal-vip
. Is this OK?
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'm going to approve it, but not LGTM. Change the domain name and then LGTM is easy.
/lgtm |
LGTM label has been added. Git tree hash: 769a3ecc3d8d347c1c3cd431c9921c4a5bda2e6d
|
What type of PR is this?
/kind failing-test
/kind flake
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #119452
Special notes for your reviewer:
The failure is after #118895.
/cc @RyanAoh
This test is flake not failing every time.
Does this PR introduce a user-facing change?