-
Notifications
You must be signed in to change notification settings - Fork 98
Move knative-local-gateway service to istio-system. #388
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
Move knative-local-gateway service to istio-system. #388
Conversation
Codecov Report
@@ Coverage Diff @@
## master #388 +/- ##
==========================================
- Coverage 81.32% 81.26% -0.06%
==========================================
Files 15 15
Lines 1012 1009 -3
==========================================
- Hits 823 820 -3
Misses 110 110
Partials 79 79
Continue to review full report at Codecov.
|
04c578c
to
251eb1f
Compare
@ZhiminXiang can you please help review this? Thanks |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JRBANCEL, ZhiminXiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a fatal in my plan to collocate both Ingress and Local Gateways into the same Envoy Pods: k8s service selectors only work inside the same namespace (the Envoy Pods are in
istio-system
).This moves the
knative-local-gateway
k8s service toistio-system
, this is fine because this service is not being used yet (see phase #2 of the plan).Also, this addresses @mattmoor comment about using
network.GetServiceHostname
.