MeshProxyPatch
The MeshProxyPatch
provides configuration options for low-level Envoy resources that Kuma policies do not directly expose.
If you need features that aren’t available as a Kuma policy, open a new issue on GitHub so they can be added to the Kuma roadmap.
A MeshProxyPatch
policy can modify:
This policy uses a new policy matching algorithm. Do not combine with Proxy Template.
targetRef
support matrix
targetRef |
Allowed kinds |
---|---|
targetRef.kind |
Mesh , MeshSubset |
To learn more about the information in this table, see the matching docs.
Configuration
Modifications
MeshProxyPatch
lets you specify modifications in appendModification
block that can add a new resource, patch an existing resource or remove an existing resource.
Each xDS resource modification consists of 3 fields:
operation
- operation applied to the generated config (for example:Add
,Remove
,Patch
).match
- some operations can be applied on matched resources (for example: remove only resource of given name, patch all outbound resources).
and one of
-
jsonPatches
- list of modifications in JSON Patch notation. -
value
- raw Envoy xDS configuration. Can be partial if operation ispatch
.
Origin
All resources generated by Kuma are marked with the origin
value, so you can match specific resources.
Examples: add new filters but only on inbound listeners, set timeouts on outbound clusters.
Well known origins:
inbound
- resources generated for incoming traffic.outbound
- resources generated for outgoing traffic.transparent
- resources generated for transparent proxy functionality.prometheus
- resources generated for Prometheus to scrape when metrics on the Mesh is enabled.direct-access
- resources generated for Direct Access functionality.gateway
- resources generated for MeshGateway.
The list is not complete, as policy plugins can introduce new resources.
For example MeshTrace plugin can create Cluster
with mesh-trace
origin.
Cluster
Modifications that are applied on Clusters resources.
Available operations:
Add
- add a new Cluster or replace existing if the name is the same.Remove
- remove a Cluster.Patch
- patch a part of Cluster definition.
Available matchers:
name
- name of the Cluster.origin
- origin of the Cluster.
Listener
Modifications that are applied on Listeners resources.
Available operations:
Add
- add a new Listener or replace existing if the name is the same.Remove
- remove a Listener.Patch
- patch a part of Listener definition.
Available matchers:
name
- name of the Listener.origin
- origin of the Listener.tags
- tags of inbound or outbound Listeners. They matchListener.metadata.filterMetadata[io.kuma.tags]
in XDS configuration.
Network Filter
Modifications that are applied on Network Filters that are part of Listeners resource. Modifications are applied on all Filter Chains in the Listener.
Available operations:
AddFirst
- add a new filter as a first filter in Filter Chain.AddLast
- add a new filter as a last filter in Filter Chain.AddAfter
- add a new filter after other filter in Filter Chain that is matched usingmatch
section.AddBefore
- add a new filter before other filter in Filter Chain that is matched usingmatch
section.Patch
- patch a matched filter in Filter Chain.Remove
- remove a filter in Filter Chain.
Available matchers:
name
- name of the Network Filter.listenerName
- name of the Listener.listenerTags
- tags of inbound or outbound Listeners. They matchListener.metadata.filterMetadata[io.kuma.tags]
in XDS configuration.origin
- origin of the Listener.
HTTP Filter
Modifications that are applied on HTTP Filters that are part of Listeners resource. Modifications that Kuma applies on all HTTP Connection Managers in the Listener.
HTTP Filter modifications can only be applied on services configured as HTTP.
Available operations:
AddFirst
- add a new filter as a first filter in HTTP Connection Manager.AddLast
- add a new filter as a last filter in HTTP Connection Manager.AddAfter
- add a new filter after other filter in HTTP Connection Manager that is matched usingmatch
section.AddBefore
- add a new filter before other filter in HTTP Connection Manager that is matched usingmatch
section.Patch
- patch a matched filter in HTTP Connection Manager.Remove
- remove a filter in HTTP Connection Manager.
Available matchers:
name
- name of the HTTP Filter.listenerName
- name of the Listener.listenerTags
- tags of inbound or outbound Listeners. They matchListener.metadata.filterMetadata[io.kuma.tags]
in XDS configuration.origin
- origin of the Listener.
VirtualHost
Modifications that are applied on VirtualHost resources.
VirtualHost modifications can only be applied on services configured as HTTP.
Available operations:
Add
- add a new VirtualHost.Remove
- remove a VirtualHost.Patch
- patch a part of VirtualHost definition.
Available matchers:
name
- name of the VirtualHost.origin
- origin of the VirtualHost.routeConfigurationName
- name of the RouteConfiguration.
Merging
All modifications from appendModification
list are always merged.
For example, if there is a policy with targetRef.kind: Mesh
and second policy with targetRef.kind: MeshService
that matches a data plane proxy,
all modifications from both policies will be applied.
JSONPatch
If you use JSONPatch, remember to always use camelCase instead of snake_case in path
parameter even though you see snake_case in Envoy Config Dump.
Examples
Timeout adjustment for MeshGateway
Example how to change streamIdleTimeout
for MeshGateway
:
lua filter
Here is and example of lua filter that adds the new x-header: test
header to all outgoing HTTP requests to service offers
.