Initially, we were going to deprecate in 2.3.1. Jacek suggested listing as KI and then deprecating in 2.4.

The proposed deprecation write-up:

The `concurrency` field of the `spec.proxy` API is deprecated as of release 2.3.1, and is planned for removal in a future release. Although the field is still supported in release 2.3.1, customers should begin using the `concurrency` field of the `ProxyConfig` API.

In the SMCP, `ProxyConfig` is the equivalent of `spec.proxy.concurrency`. The `concurrency` field specifies the number of worker threads to run. If the field is set to `0`, then the number of worker threads available is equal to the number of CPU cores. If the field is not set, then the number of worker threads available defaults to `2`.

In the following example, the `concurrency` field is set to `0`.

[source,yaml]

apiVersion: networking.istio.io/v1beta1
kind: ProxyConfig
metadata:
name: mesh-wide-concurrency
namespace: <istiod-namespace>
spec:
concurrency: 0

For reference: OSSM-2317, OSSM-1115

cc: jewertow@redhat.com, dgrimm@redhat.com