docs(README): update to modern targetRef policies

README.md

@@ -68,27 +68,32 @@ Below is an example of using Kuma's attributes to route all traffic generated by
 
 ```yaml
 apiVersion: kuma.io/v1alpha1
-kind: TrafficRoute
+kind: MeshHTTPRoute
 mesh: default
 metadata:
   name: ch-pci-compliance
 spec:
-  sources:
-    - match:
-        kuma.io/service: '*'
-        kuma.io/zone: 'CH'
-        PCI: true
-  destinations:
-    - match:
-        kuma.io/service: '*'
-  conf:
-    loadBalancer:
-      roundRobin: {}
-    split:
-      - weight: 100
-        destination:
-          kuma.io/service: '*'
-          kuma.io/zone: 'CH'
+  targetRef:
+    kind: MeshSubset
+    tags:
+      kuma.io/zone: CH
+      PCI: "true"
+  to:
+    - targetRef:
+        kind: MeshService
+        name: backend
+      rules:
+        - matches:
+            - path:
+                type: PathPrefix
+                value: /
+          default:
+            backendRefs:
+              - kind: MeshServiceSubset
+                name: backend
+                tags:
+                  kuma.io/zone: CH
+                weight: 100
 ```
 
 The above example can also be applied on virtual machines via the built-in `kumactl` CLI.
@@ -109,13 +114,13 @@ With Kuma, our application teams can stop building connectivity management code
 * **mTLS**: Automatic mTLS issuing, identity and encryption with optional support for third-party CA.
 * **TLS Rotation**: Automatic certificate rotation for all the data planes, with configurable settings.
 * **Internal & External Services**: Aggregation of internal services and support for services outside the mesh.
-* **Traffic Permissions**: To firewall traffic between the services of a Mesh.
-* **Traffic Routing**: With dynamic load-balancing for blue/green, canary, versioning and rollback deployments.
-* **Fault Injection**: To harden our systems by injecting controlled artificial faults and observe the behavior.
-* **Traffic Logs**: To log all the activity to a third-party service, like Splunk or ELK.
-* **Traffic Tracing**: To observe the full trace of the service traffic and determine bottlenecks.
-* **Traffic Metrics**: For every Envoy dataplane managed by Kuma with native Prometheus/Grafana support.
-* **Retries**: To improve application reliability by automatically retrying requests.
+* **MeshTrafficPermission**: To firewall traffic between services with zero-trust security.
+* **MeshHTTPRoute & MeshTCPRoute**: With dynamic load-balancing for blue/green, canary, versioning and rollback deployments.
+* **MeshFaultInjection**: To harden systems by injecting controlled artificial faults and observe behavior.
+* **MeshAccessLog**: To log all activity to third-party services, like Splunk or ELK.
+* **MeshTrace**: To observe the full trace of service traffic and determine bottlenecks.
+* **MeshMetric**: For every Envoy dataplane managed by Kuma with native Prometheus/Grafana support.
+* **MeshRetry**: To improve application reliability by automatically retrying requests.
 * **Proxy Configuration Templating**: The easiest way to run and configure Envoy with low-level configuration.
 * **Gateway Support**: To support any API Gateway or Ingress, like [Kong Gateway](https://github.com/Kong/kong).
 * **Healthchecks**: Both active and passive.