Open Service Mesh (OSM) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.
Please describe the Improvement and/or Feature Request
The ability to set custom Envoy configuration when using Open Service Mesh. For example setting the lb_policy to use a different load balancer policy.
Apologies if this is already possible. I couldn't find anything in the documentation. I can see that it's possible to set the Envoy image used by setting spec.sidecar.envoyImage in the mesh configuration so I could build a custom image with that configuration but I'm unsure what side affects that might cause and is much more effort to maintain.
There is an example of Envoy config being provided in a configmap here but it's not clear how that configmap can be referenced when installing OSM via AKS.
Scope (please mark with X where applicable)
New Functionality [ ]
Install [ ]
SMI Traffic Access Policy [ ]
SMI Traffic Specs Policy [ ]
SMI Traffic Split Policy [ ]
Permissive Traffic Policy [ ]
Ingress [ ]
Egress [ ]
Envoy Control Plane [X]
CLI Tool [ ]
Metrics [ ]
Certificate Management [ ]
Sidecar Injection [ ]
Logging [ ]
Debugging [ ]
Tests [ ]
CI System [ ]
Demo [ ]
Project Release [ ]
Possible use cases
Overriding the default lb_policy to allow for other algorithms such as RING_HASH or MAGLEV.
Please describe the Improvement and/or Feature Request The ability to set custom Envoy configuration when using Open Service Mesh. For example setting the lb_policy to use a different load balancer policy.
Apologies if this is already possible. I couldn't find anything in the documentation. I can see that it's possible to set the Envoy image used by setting
spec.sidecar.envoyImage
in the mesh configuration so I could build a custom image with that configuration but I'm unsure what side affects that might cause and is much more effort to maintain.There is an example of Envoy config being provided in a configmap here but it's not clear how that configmap can be referenced when installing OSM via AKS.
Scope (please mark with X where applicable)
Possible use cases Overriding the default
lb_policy
to allow for other algorithms such asRING_HASH
orMAGLEV
.