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
Add appProtocol to agent service to allow agent to work with istio #5240
base: master
Are you sure you want to change the base?
Add appProtocol to agent service to allow agent to work with istio #5240
Conversation
Signed-off-by: noahjax <noah.jackson@dominodatalab.com>
I think you just need to run the local tools to update the generated files and such:
|
Signed-off-by: noahjax <noah.jackson@dominodatalab.com>
@@ -40,6 +40,7 @@ spec: | |||
- name: agent-grpc | |||
port: 8000 | |||
protocol: TCP | |||
appProtocol: TCP |
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.
🙌
Signed-off-by: noahjax <noah.jackson@dominodatalab.com>
Signed-off-by: noahjax <noah.jackson@dominodatalab.com>
14660e5
to
bbcefcd
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5240 +/- ##
==========================================
- Coverage 58.60% 58.15% -0.46%
==========================================
Files 568 204 -364
Lines 51121 15429 -35692
==========================================
- Hits 29958 8972 -20986
+ Misses 18748 5627 -13121
+ Partials 2415 830 -1585
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@noahjax could you run |
I'll take this one over too and try to update tomorrow. Thanks! |
Why are the changes needed?
If you try to use an agent on a cluster with istio, flytepropeller is unable to connect to the agent. You will either need to remove the agent from flytepropeller's configmap or flytepropeller will fail on startup.
Connecting to flyteconsole is also broken in istio because missing appProtocol prevents some http ports from working correctly.
What changes were proposed in this pull request?
Specify an
appProtocol
that istio can use to determine how to proxy requests (see here for more details on how this works).Update: I also modified the flyteadmin and flyteconsole services so that they will work with istio as well. More extensive changes are necessary to get everything working, but I will split those into a separate PR as they are likely more controversial
How was this patch tested?
Tested on my flyte deployment with istio enabled for the whole cluster.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link