-
Notifications
You must be signed in to change notification settings - Fork 89
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
Test sandwiched waypoint #973
Conversation
Skipping CI for Draft Pull Request. |
2622ad5
to
15285a9
Compare
@@ -233,7 +233,7 @@ impl OutboundConnection { | |||
.track_outbound(source_addr, dest_addr, req.gateway); | |||
|
|||
let metrics = self.pi.metrics.clone(); | |||
let hbone_target = if req.request_type == RequestType::ToServerWaypoint { | |||
let hbone_target = if req.protocol == Protocol::HBONE { |
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.
minor fix to make stats properly report for all hbone cases, not just to waypoint
@@ -48,7 +48,6 @@ pub struct WorkloadManager { | |||
services: HashMap<NamespacedHostname, Service>, | |||
/// Configured policies | |||
policies: Vec<Authorization>, | |||
waypoints: Vec<IpAddr>, |
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 needed anymore, waypoints are not special. This was deadcode before this PR
let waypoint = manager | ||
.workload_builder("waypoint", DEFAULT_NODE) | ||
.mutate_workload(|w| { | ||
w.application_tunnel = Some(ApplicationTunnel { |
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 doesn't really do anything, is it just here for explicitness?
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.
TBH thought it did matter... I was thinking of adding a PROXY test as well but didn't get around to it
In response to a cherrypick label: #973 failed to apply on top of branch "release-1.22":
|
In response to a cherrypick label: new issue created for failed cherrypick: #976 |
/cherry-pick release-1.22 |
@bleggett: new pull request created: #984 In response to this:
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. |
No description provided.