-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix(daemon): port mapping for compound pods #3304
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
Conversation
3e12f73
to
86b02ec
Compare
Codecov Report
@@ Coverage Diff @@
## master #3304 +/- ##
==========================================
+ Coverage 88.72% 89.81% +1.08%
==========================================
Files 152 152
8000
Lines 10806 10806
==========================================
+ Hits 9588 9705 +117
+ Misses 1218 1101 -117
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
540197c
to
1de1e5e
Compare
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 cant follow in every detail, but generally looks like a good solution for compound pods to me 👍
This addresses issues with port-mapping, when inside a remote Flow, we start a CompoundPod which uses ContainerRuntime. So the
head
&tail
Peas live inside the Flow container & they need to be set/exposed correctly inside main-daemon & partial-daemon. With this PR, we have introducedPortMappings
which take a json ofpod_name
,pea_name
& corresponding Ports.