-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Ensure the mesh gateway configuration comes back in the api within each upstream #6093
Ensure the mesh gateway configuration comes back in the api within each upstream #6093
Conversation
} | ||
|
||
// if the default mode | ||
if meshGateway == structs.MeshGatewayModeDefault { | ||
meshGateway = s.proxyCfg.MeshGateway.Mode | ||
meshGateway = structs.MeshGatewayModeNone |
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.
Perhaps a test for this behavior you modified in the proxycfg
package would be good.
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 totally sure, but I think if this new Kind index is necessary for delete correctness then there is one branch here still missing updates.
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.
Nice those tests look like a good way to validate this without lots more timing-sensitive code and elaborate mocking.
Also start implementing proxycfg state testing.
0bb6919
to
885646f
Compare
…rgets of a discovery chain.
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
Fixes #6085
• Fixes the ToAPI method on the Upstream to properly convert the MeshGatewayConfig so it doesn't get returned as empty.
• Fixes a service dump kind blocking issue that caused it not to wake up the watcher when a service of that kind was deleted (or its check/node were deleted)
• Fixes another issue that caused mesh gateways to be used even for dc local connections.