clarified the timestamp should be in nanoseconds

Author: SergeyKanzhelev

staging/src/k8s.io/cri-api/pkg/apis/runtime/v1/api.pb.go

@@ -601,7 +601,7 @@ message PodSandboxStatusResponse {
     map<string, string> info = 2;
     // Container statuses
     repeated ContainerStatus containers_statuses = 3;
-    // Timestamp at which container and pod statuses were recorded
+    // Timestamp in nanoseconds at which container and pod statuses were recorded
     int64 timestamp = 4;
 }
 
@@ -1344,7 +1344,7 @@ message ContainerResources {
 
 message ContainerUser {
     // User identities initially attached to first process in the Linux container.
-	// Note that the actual running identity can be changed if the process has enough privilege to do so.
+    // Note that the actual running identity can be changed if the process has enough privilege to do so.
     LinuxContainerUser linux = 1;
 
     // User identities initially attached to first process in the Windows container
@@ -1863,7 +1863,7 @@ message ContainerEventResponse {
     // Type of the container event
     ContainerEventType container_event_type = 2;
 
-    // Creation timestamp of this event
+    // Creation timestamp in nanoseconds of this event
     int64 created_at = 3;
 
     // Sandbox status
@@ -1927,7 +1927,7 @@ message Metric {
     // otherwise, it will be ignored.
     string name = 1;
     // Timestamp should be 0 if the metric was gathered live.
-    // If it was cached, the Timestamp should reflect the time it was collected.
+    // If it was cached, the Timestamp should reflect the time in nanoseconds it was collected.
     int64 timestamp = 2;
     MetricType metric_type = 3;
     // The corresponding LabelValues to the LabelKeys defined in the MetricDescriptor.