-
Notifications
You must be signed in to change notification settings - Fork 337
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
feat(kuma-cp) add ServiceAddress to dataplane Inbound #892
Conversation
Signed-off-by: Nikolay Nikolaev <[email protected]>
Signed-off-by: Nikolay Nikolaev <[email protected]>
…t, ParseIP Signed-off-by: Nikolay Nikolaev <[email protected]>
Will it work in Kubernetes with transparent proxy mode? If not, we need somehow show that this property should be used only on Universal, maybe we can add validation. |
Signed-off-by: Nikolay Nikolaev <[email protected]>
Signed-off-by: Nikolay Nikolaev <[email protected]>
} | ||
return text, nil | ||
} | ||
|
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.
Awesome, thank's for cleaning it up.
if inbound.ServicePort == 0 || inbound.ServicePort == inbound.Port { | ||
result.AddViolationAt(validators.RootedAt("serviceAddress"), `serviceAddress and servicePort has to differ from inboundIP and Port`) | ||
} | ||
} |
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.
can you add tests for those new cases?
Signed-off-by: Nikolay Nikolaev <[email protected]>
address: 1.1.1.1 | ||
tags: | ||
service: backend`, | ||
}), |
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.
We've got should pass validation
section above
Signed-off-by: Nikolay Nikolaev <[email protected]>
Summary
As described in #891, we would like to extend the DataplaneResource to include a ServiceAddress field in the Inbound. This way the dataplane and the service can live in different IP netns, containers, VMs etc.
Remove the remains of the
Interface
remove in #832. In the dataplaen helpers deletedParseInboundInterface
,ParseOutboundInterface
,ParsePort
,ParseIP
.Full changelog
Issues resolved
Fix #891
Documentation