-
Notifications
You must be signed in to change notification settings - Fork 9
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: peer to peer routing #3599
Conversation
1c0a7b4
to
f367d7c
Compare
b456380
to
b33868c
Compare
6f6a00e
to
a688d4b
Compare
fedc798
to
d9c4c2f
Compare
18c2c40
to
975e6db
Compare
361a8fd
to
a8c93e4
Compare
c7c9bb8
to
78fe647
Compare
@@ -46,7 +43,7 @@ func (c cronJob) String() string { | |||
} | |||
|
|||
// Start the cron service. Blocks until the context is cancelled. | |||
func Start(ctx context.Context, eventSource schemaeventsource.EventSource, verbClient CallClient) error { | |||
func Start(ctx context.Context, eventSource schemaeventsource.EventSource, client routing.CallClient) error { |
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.
Mmm cron makes me think - we'll need to have Istio rules for which FTL services can access what...not just verbs.
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.
Ah yea, I already have that to allow the controller and provisioner to allow access. I will update it to allow ingress and cron for modules that need those services.
966b746
to
bb63ba6
Compare
I am going to disable the rolling deployment part of the kube tests, I don't think there is any point in worrying about that until well after the refactor is done. |
6689d36
to
5e64208
Compare
5e64208
to
968d22b
Compare
968d22b
to
c5a38de
Compare
No description provided.