kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add comment about frameworks that could use this feature

This commit is contained in:
Brad Hoekstra 2018-11-06 10:20:37 -05:00
parent 68029a440d
commit 74798ecb09
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
keps/sig-network/0031-20181017-kube-proxy-services-optional.md
View File

@ -86,6 +86,8 @@ The envisioned cluster that will make use of this feature looks something like t
* These small number of entry points into the cluster are a part of the service mesh
* There are many micro-services in the cluster, all a part of the service mesh, that are only accessed from inside the service mesh
Higher level frameworks built on top of service meshes, such as [Knative](https://github.com/knative/docs), will be able to enable this feature by default due to having a more controlled application/service model and being reliant on the service mesh.
#### Design
Currently, when ProxyServer starts up it creates informers for all Service (ServiceConfig) and Endpoints (EndpointsConfig) objects using a single shared informer factory.