Fix api version properly

Signed-off-by: Alex Leong <[email protected]>

traffic-metrics.md

@@ -51,7 +51,7 @@ The core resource is `TrafficMetrics`. It references a `resource`, has an `edge`
 and surfaces latency percentiles and request volume.
 
 ```yaml
-apiVersion: metrics.smi-spec.io/v1alpha1
+apiVersion: metrics.smi-spec.io/v1alpha2
 kind: TrafficMetrics
 # See ObjectReference v1 core for full spec
 resource:
@@ -150,7 +150,7 @@ There are three different ways to get a TrafficMetricsList:
 * Requesting a specific `kind` such as pods or namespaces.
 
     ```yaml
-    apiVersion: metrics.smi-spec.io/v1alpha1
+    apiVersion: metrics.smi-spec.io/v1alpha2
     kind: TrafficMetricsList
     resource:
       kind: Pod
@@ -164,7 +164,7 @@ There are three different ways to get a TrafficMetricsList:
 * Requesting a specific `kind` such as pods and filtering with a label selector:
 
     ```yaml
-    apiVersion: metrics.smi-spec.io/v1alpha1
+    apiVersion: metrics.smi-spec.io/v1alpha2
     kind: TrafficMetricsList
     resource:
       kind: Pod
@@ -181,7 +181,7 @@ There are three different ways to get a TrafficMetricsList:
 * Listing all the edges for a specific resource:
 
     ```yaml
-    apiVersion: metrics.smi-spec.io/v1alpha1
+    apiVersion: metrics.smi-spec.io/v1alpha2
     kind: TrafficMetricsList
     resource:
       name: foo-775b9cbd88-ntxsl
@@ -207,20 +207,20 @@ kind: APIService
 metadata:
   name: v1alpha1.metrics.smi-spec.io
 spec:
-  group: metrics.smi-spec.io/v1alpha1
+  group: metrics.smi-spec.io/v1alpha2
   service:
     name: mesh-metrics
     namespace: default
   version: v1alpha1
 ```
 
-The default response, or requesting `/apis/metrics.smi-spec.io/v1alpha1/`
+The default response, or requesting `/apis/metrics.smi-spec.io/v1alpha2/`
 would return:
 
 ```yaml
 apiVersion: v1
 kind: APIResourceList
-groupVersion: metrics.smi-spec.io/v1alpha1
+groupVersion: metrics.smi-spec.io/v1alpha2
 resources:
 - name: namespaces
   namespaced: false
@@ -270,7 +270,7 @@ and contains a `backend` field which indicates to which backend those metrics
 correspond.
 
 ```yaml
-apiVersion: metrics.smi-spec.io/v1alpha1
+apiVersion: metrics.smi-spec.io/v1alpha2
 kind: TrafficMetrics
 # See ObjectReference v1 core for full spec
 resource:
@@ -312,7 +312,7 @@ route only. If the `route` field is empty, the traffic metrics apply to the
 resource as a whole.
 
 ```yaml
-apiVersion: metrics.smi-spec.io/v1alpha1
+apiVersion: metrics.smi-spec.io/v1alpha2
 kind: TrafficMetrics
 # See ObjectReference v1 core for full spec
 resource:
@@ -445,7 +445,7 @@ Walking through the request flow:
 1. An end user fires off a request to the Kubernetes API Server:
 
     ```bash
-    kubectl get --raw /apis/metrics.smi-spec.io/v1alpha1/namespaces/default/deployments/
+    kubectl get --raw /apis/metrics.smi-spec.io/v1alpha2/namespaces/default/deployments/
     ```
 
 1. The Kubernetes API server forwards this request to the `Traffic Metrics

traffic-specs.md

@@ -19,7 +19,7 @@ This resource is used to describe HTTP/1 and HTTP/2 traffic. It enumerates the
 routes that can be served by an application.
 
 ```yaml
-apiVersion: specs.smi-spec.io/v1alpha2
+apiVersion: specs.smi-spec.io/v1alpha1
 kind: HTTPRouteGroup
 metadata:
   name: the-routes