Fix output variable length issue - KubernetesV1 (#11525)

Author: ajinkya599

Tasks/KubernetesV1/src/kubernetes.ts

@@ -107,11 +107,12 @@ function executeKubectlCommand(clusterConnection: ClusterConnection, command: st
     return commandImplementation.run(clusterConnection, command, (data) => result.push(data))
         .fin(function cleanup() {
             console.log("commandOutput" + result);
-            var commandOutputLength = result.length;
+            const resultString = result.toString();
+            const commandOutputLength = resultString.length;
             if (commandOutputLength > environmentVariableMaximumSize) {
                 tl.warning(tl.loc("OutputVariableDataSizeExceeded", commandOutputLength, environmentVariableMaximumSize));
             } else {
-                tl.setVariable('KubectlOutput', result.toString());
+                tl.setVariable('KubectlOutput', resultString);
             }
 
             const outputFormat: string = tl.getInput("outputFormat", false);

Tasks/KubernetesV1/task.json

@@ -14,7 +14,7 @@
     "version": {
         "Major": 1,
         "Minor": 158,
-        "Patch": 1
+        "Patch": 2
     },
     "demands": [],
     "releaseNotes": "What's new in Version 1.0:<br/>&nbsp;Added new service connection type input for easy selection of Azure AKS cluster.<br/>&nbsp;Replaced output variable input with output variables section that we had added in all tasks.",

Tasks/KubernetesV1/task.loc.json

@@ -14,7 +14,7 @@
   "version": {
     "Major": 1,
     "Minor": 158,
-    "Patch": 1
+    "Patch": 2
   },
   "demands": [],
   "releaseNotes": "ms-resource:loc.releaseNotes",