--- title: ProxyConfig description: Provides configuration for individual workloads. location: https://istio.io/docs/reference/config/networking/proxy-config.html layout: protoc-gen-docs generator: protoc-gen-docs schema: istio.networking.v1beta1.ProxyConfig aliases: [/docs/reference/config/networking/v1beta1/proxy-config] number_of_entries: 2 ---

`ProxyConfig` exposes proxy level configuration options. `ProxyConfig` can be configured on a per-workload basis, a per-namespace basis, or mesh-wide. `ProxyConfig` is not a required resource; there are default values in place, which are documented inline with each field.

NOTE: fields in ProxyConfig are not dynamically configured - changes will require restart of workloads to take effect.

For any namespace, including the root configuration namespace, it is only valid to have a single workload selector-less `ProxyConfig` resource.

For resources with a workload selector, it is only valid to have one resource selecting any given workload.

For mesh level configuration, put the resource in the root configuration namespace for your Istio installation without a workload selector:

    apiVersion: networking.istio.io/v1beta1
    kind: ProxyConfig
    metadata:
      name: my-proxyconfig
      namespace: istio-system
    spec:
      concurrency: 0
      image:
        imageType: distroless

For namespace level configuration, put the resource in the desired namespace without a workload selector:

    apiVersion: networking.istio.io/v1beta1
    kind: ProxyConfig
    metadata:
      name: my-ns-proxyconfig
      namespace: user-namespace
    spec:
      concurrency: 0

For workload level configuration, set the `selector` field on the `ProxyConfig` resource:

    apiVersion: networking.istio.io/v1beta1
    kind: ProxyConfig
    metadata:
      name: per-workload-proxyconfig
      namespace: example
    spec:
      selector:
        matchLabels:
          app: ratings
      concurrency: 0
      image:
        imageType: debug

If a `ProxyConfig` CR is defined that matches a workload it will merge with its `proxy.istio.io/config` annotation if present, with the CR taking precedence over the annotation for overlapping fields. Similarly, if a mesh wide `ProxyConfig` CR is defined and `meshConfig.DefaultConfig` is set, the two resources will be merged with the CR taking precedence for overlapping fields.

## ProxyConfig

`ProxyConfig` exposes proxy level configuration options.

Field | Type | Description | Required
--- | --- | --- | ---
`selector` | `WorkloadSelector` | Optional. Selectors specify the set of pods/VMs on which this `ProxyConfig` resource should be applied. If not set, the `ProxyConfig` resource will be applied to all workloads in the namespace where this resource is defined. | No
`concurrency` | `Int32Value` | The number of worker threads to run. If unset, this will be automatically determined based on CPU limits. If set to 0, all cores on the machine will be used. | No
`environmentVariables` | `map<string, string>` | Additional environment variables for the proxy. Names starting with `ISTIO_META_` will be included in the generated bootstrap configuration and sent to the XDS server. | No
`image` | `ProxyImage` | Specifies the details of the proxy image. | No

## ProxyImage

The following values are used to construct proxy image url. format: `${hub}/${image_name}/${tag}-${image_type}`, example: `docker.io/istio/proxyv2:1.11.1` or `docker.io/istio/proxyv2:1.11.1-distroless`. This information was previously part of the Values API.

Field | Type | Description | Required
--- | --- | --- | ---
`imageType` | `string` | The image type of the image. Istio publishes default, debug, and distroless images. Other values are allowed if those image types (example: centos) are published to the specified hub. supported values: default, debug, distroless. | No