feat: worker label
reason: without a unique label set, you cannot access the pods for a worker deployment uniquely. this is a flexible approach. should pass in the worker name as label?
this does not seem to correct the issue of:
kubectl logs deployments.apps/${release_name}-${worker_name} -n $KUBE_NAMESPACE
returns
Found 2 pods, using pod/${release_name}-${worker_name}-{slug}
pod-template-hash seems unique yet the logs call on a deployment picks up another deployment logs on the same tier.
Edited by Don Kendall