add task api endpoint in oci proto

Signed-off-by: Abel Feng <[email protected]>

Author: abel-von

core/runtime/v2/runc/options/next.pb.txt

@@ -73,6 +73,27 @@ file {
       type: TYPE_STRING
       json_name: "criuWorkPath"
     }
+    field {
+      name: "task_api_address"
+      number: 12
+      label: LABEL_OPTIONAL
+      type: TYPE_STRING
+      json_name: "taskApiAddress"
+    }
+    field {
+      name: "task_api_protocol"
+      number: 13
+      label: LABEL_OPTIONAL
+      type: TYPE_STRING
+      json_name: "taskApiProtocol"
+    }
+    field {
+      name: "task_api_version"
+      number: 14
+      label: LABEL_OPTIONAL
+      type: TYPE_UINT32
+      json_name: "taskApiVersion"
+    }
     reserved_range {
       start: 8
       end: 9

core/runtime/v2/runc/options/oci.pb.go

@@ -29,6 +29,12 @@ message Options {
 	string criu_image_path = 10;
 	// criu work path
 	string criu_work_path = 11;
+	// task api address, can be a unix domain socket, or vsock address.
+	string task_api_address = 12;
+	// protocol for task api connection, currently ttrpc and grpc supported
+	string task_api_protocol = 13;
+	// task api version, currently supported value is 2 and 3.
+	uint32 task_api_version = 14;
 }
 
 message CheckpointOptions {