consul/connect: enable setting consul namespace for upstream

[MVJosh]

As described in #13121, Nomad enterprise doesn't currently provide the ability to specify which Consul namespace a Connect service should point at via a Connect upstream.

Apologies if this is a duplicate, but as far as I can tell no other open issue addresses this specific point.

I believe the previous issue may have been closed by mistake. Several other related issues are referenced, which cover similar but different features:

• connect: enable setting destination type in connect upstream  #13138 covers setting destination_type in connect upstream.
• consul: support for admin partitions #13139 covers setting destination_partition.
• consul/connect: enable setting consul namespace for gateway config entries #13123 covers setting Consul namespace for gateway config entries.

None of the above cover setting destination_namespace for connect upstream.

[tgross]

I'm pretty sure this is entirely covered in the work-to-be done for admin partitions, but that's ok, we'll keep this open.

[MVJosh]

Apologies @tgross I may be misunderstanding the relationship between admin partitions & namespaces in consul. I'm currently working with namespaces but not making use of admin partitions.

In any case, it looks like this feature was added by #13125 but not released yet - I must have missed that before as it wasn't referenced by the original issue.

[shoenig]

Yeah sorry @MVJosh, that PR should be in Nomad 1.3.2, which should be shipping in the next few days

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.