[BUG]: Duplicated output in Kubernetes task (minor nuisance), reraised as original issue not addressed

[david-creigh-msi]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

Kubernetes

Task version

1.227.0

Issue Description

Output of Kubernetes commands are duplicated in AzDO output with the word commandOutput between the first and second copies.

Previously raised in #18481 but I missed the "stale tag" notification.

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

ubuntu-20.04

Relevant log output

==============================================================================
Prepending PATH environment variable with directory: /usr/local/bin
==============================================================================
			Kubectl Client Version: v1.26.2
			Kubectl Server Version: v1.21.14
==============================================================================
/usr/local/bin/kubectl get pods
NAME                                              READY   STATUS    RESTARTS   AGE
arbitrary-pod-123                                 1/1     Running   0          3d21h
arbitrary-pod-456                                 1/1     Running   0          3d21h
commandOutputNAME                                              READY   STATUS    RESTARTS   AGE
arbitrary-pod-123                                 1/1     Running   0          3d21h
arbitrary-pod-456                                 1/1     Running   0          3d21h


(I have redacted the names of our actual pods)

Repro steps

After the output of the task, the string commandOutput appears and then the entire output is repeated.

### Suggested fix

Appears to be console logging here. Guessing this was used for local testing of the task during initial development?

[dumasc-ciandt]

Any news about this issue?

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days