fix leftovers

Signed-off-by: ChrsMark <chrismarkou92@gmail.com>

model/k8s/deprecated/metrics-deprecated.yaml

@@ -4,8 +4,7 @@ groups:
     metric_name: k8s.replication_controller.desired_pods
     stability: experimental
     deprecated: "Replaced by `k8s.replicationcontroller.desired_pods`."
-    brief: "Deprecated, use `k8s.replication_controller.desired_pods` instead."
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
+    brief: "Deprecated, use `k8s.replicationcontroller.desired_pods` instead."
     note: |
       This metric aligns with the `replicas` field of the
       [K8s ReplicationControllerSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#replicationcontrollerspec-v1-core)
@@ -19,8 +18,7 @@ groups:
     metric_name: k8s.replication_controller.available_pods
     stability: experimental
     deprecated: "Replaced by `k8s.replicationcontroller.available_pods`."
-    brief: "Deprecated, use `k8s.replication_controller.available_pods` instead."
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
+    brief: "Deprecated, use `k8s.replicationcontroller.available_pods` instead."
     note: |
       This metric aligns with the `availableReplicas` field of the
       [K8s ReplicationControllerStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#replicationcontrollerstatus-v1-core)

model/k8s/metrics.yaml

@@ -189,7 +189,6 @@ groups:
     metric_name: k8s.replicationcontroller.desired_pods
     stability: experimental
     brief: "Number of desired replica pods in this replication controller"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `replicas` field of the
       [K8s ReplicationControllerSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#replicationcontrollerspec-v1-core)
@@ -203,7 +202,6 @@ groups:
     metric_name: k8s.replicationcontroller.available_pods
     stability: experimental
     brief: "Total number of available replica pods (ready for at least minReadySeconds) targeted by this replication controller"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `availableReplicas` field of the
       [K8s ReplicationControllerStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#replicationcontrollerstatus-v1-core)
@@ -273,7 +271,6 @@ groups:
     metric_name: k8s.hpa.desired_pods
     stability: experimental
     brief: "Desired number of replica pods managed by this horizontal pod autoscaler, as last calculated by the autoscaler"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `desiredReplicas` field of the
       [K8s HorizontalPodAutoscalerStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#horizontalpodautoscalerstatus-v2-autoscaling)
@@ -287,7 +284,6 @@ groups:
     metric_name: k8s.hpa.current_pods
     stability: experimental
     brief: "Current number of replica pods managed by this horizontal pod autoscaler, as last seen by the autoscaler"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `currentReplicas` field of the
       [K8s HorizontalPodAutoscalerStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#horizontalpodautoscalerstatus-v2-autoscaling)
@@ -301,7 +297,6 @@ groups:
     metric_name: k8s.hpa.max_pods
     stability: experimental
     brief: "The upper limit for the number of replica pods to which the autoscaler can scale up"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `maxReplicas` field of the
       [K8s HorizontalPodAutoscalerSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#horizontalpodautoscalerspec-v2-autoscaling)
@@ -315,7 +310,6 @@ groups:
     metric_name: k8s.hpa.min_pods
     stability: experimental
     brief: "The lower limit for the number of replica pods to which the autoscaler can scale down"
-    # TODO: Add note for resource correlation once https://github.com/open-telemetry/semantic-conventions/issues/1656 is implemented
     note: |
       This metric aligns with the `minReplicas` field of the
       [K8s HorizontalPodAutoscalerSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#horizontalpodautoscalerspec-v2-autoscaling)