Can't create k8s target in a non-default worker pool via New-OctopusKubernetesTarget command

[KennethBates]

Prerequisites

• I have verified the problem exists in the latest version
• I have searched open and closed issues to make sure it isn't already reported
• I have written a descriptive issue title
• I have linked the original source of this report
• I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

The command New-OctopusKubernetesTarget has an argument -octopusDefaultWorkerPoolIdOrName but when specifying a worker pool Id or Name here, the created k8s target isn't registered to use that worker pool. It only registers to use the default pool.

What I expected to happen

The worker pool specified in the -octopusDefaultWorkerPoolIdOrName argument should register the k8s target to use that pool.

Affected versions

Reproduced and reported in 2020.1.0

Workarounds

You have to update the target to use the non-default pool after the script is run.

Links

Reported here: https://help.octopus.com/t/powershell-command-for-adding-dynamic-kube-target-ignores-worker-pool-argument/24955