README.md is outdated

[lobkovilya]

Description

• In Why Kuma? we have an old TrafficRoute policy example

  kuma/README.md

  Lines 69 to 92 in 31ef6a2

  	```yaml
  	apiVersion: kuma.io/v1alpha1
  	kind: TrafficRoute
  	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'
  	```

• Features list is also using old policies

  kuma/README.md

  Lines 102 to 126 in 31ef6a2

  	* **Universal Control Plane**: Easy to use, distributed, runs anywhere on both Kubernetes and VM/Bare Metal.
  	* **Lightweight Data Plane**: Powered by Envoy to process any L4/L7 traffic, with automatic Envoy bootstrapping.
  	* **Automatic DP Injection**: No code changes required in K8s. Easy YAML specification for VM and Bare Metal deployments.
  	* **Multi-Mesh**: To setup multiple isolated Meshes in one cluster and one Control Plane, lowering OPs cost.
  	* **Single and Multi Zone**: To deploy a service mesh that is cross-platform, cross-cloud and cross-cluster.
  	* **Automatic Discovery & Ingress**: With built-in service discovery and connectivity across single and multi-zones.
  	* **Global & Remote CPs**: For scalability across deployments with multiple zones, including hybrid VMs + K8s meshes.
  	* **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.
  	* **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.
  	* **GUI**: Out of the box browser GUI to explore all the Service Meshes configured in the system.
  	* **Tagging Selectors**: To apply sophisticated regional, cloud-specific and team-oriented policies.
  	* **Platform-Agnostic**: Support for Kubernetes, VMs, and bare metal. Including hybrid deployments.
  	* **Transparent Proxying**: Out of the box transparent proxying on Kubernetes, VMs and any other platform.
  	* **Network Overlay**: Create a configurable Mesh overlay across different Kubernetes clusters and namespaces.

• Kuma GUI screenshot is very old as well

[lukidzi]

Triage: lets update this