k8s/controlplane: add cloud apiserver monitoring snippet

Co-authored-by: Paolo Gallina <paologallina1992@gmail.com>

src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/configure-control-plane-monitoring.mdx

@@ -174,6 +174,32 @@ For the same reason above, it is currently not possible to use autodiscovery for
 
 Lastly, `staticEndpoint` allows only to define a single endpoint per component. This means that if you have multiple control plane shards in different hosts, it is currently not possible to point to them separately. This is also a known limitation we are working to address in future versions. For the time being, a workaround could be to aggregate metrics for different shards elsewhere, and point the `staticEndpoint` URL to the aggregated output.
 
+#### Control plane monitoring for managed and cloud environments [#cloud-control-plane]
+
+Some cloud environments, like EKS or GKE, allow retrieving metrics from the Kubernetes API Server. This can be easily configured as an static endpoint:
+
+```yaml
+controlPlane:
+  affinity:
+    nodeAffinity: false  # https://github.com/helm/helm/issues/9136
+  kind: Deployment
+  config:
+    etcd:
+      enabled: false
+    scheduler:
+      enabled: false
+    controllerManager:
+      enabled: false
+    apiServer:
+     staticEndpoint:
+       url: "https://kubernetes.default:443"
+       insecureSkipVerify: true
+       auth:
+         type: bearer
+```
+
+Please note that this only applies to the API Server and that etcd, the scheduler, and the controller manager remain inaccessible in cloud environments.
+
 ## Monitoring control plane with integration version 2 [#monitoring-control-plane]
 
 This section covers how to configure control plane monitoring on versions 2 and earlier of the integration.