diff --git a/website/content/en/docs/installation/prerequisites.md b/website/content/en/docs/installation/prerequisites.md
index 58569b6..2109f31 100644
--- a/website/content/en/docs/installation/prerequisites.md
+++ b/website/content/en/docs/installation/prerequisites.md
@@ -10,12 +10,14 @@ description: >
 We recommend that you use a "[Gardener](https://gardener.cloud/)" managed cluster to deploy CAP applications that are managed with CAP Operator.
 
 The Kubernetes cluster must be set up with the following prerequisites before you install CAP Operator:
-##### [Istio](https://istio.io/latest/docs/concepts/traffic-management/) (version >= 1.12)
+##### [Istio](https://istio.io/latest/docs/concepts/traffic-management/) (version >= 1.22)
 
 Istio service mesh is used for HTTP traffic management. CAP Operator creates Istio resources to manage incoming HTTP requests to the application as well as to route requests on specific (tenant) subdomains.
 
 > It's required that you determine the public ingress Gateway subdomain and the overall shoot domain for the system and specify them in the [chart values](../../installation/helm-install/#values)
 
+> Note: Istio promoted many of its [APIs to v1 in 1.22 release](https://istio.io/latest/blog/2024/v1-apis/). Hence as of CAP Operator release v0.11.0 istio version >= 1.22 is a prerequisite.
+
 ##### [sap-btp-service-operator](https://github.com/SAP/sap-btp-service-operator) or [cf-service-operator](https://sap.github.io/cf-service-operator/docs/)
 
 These operators can be used for managing SAP BTP service instances and service bindings from within the Kubernetes cluster.