Namespaces in OSS

Please search the existing issues for relevant feature requests, and use the reaction feature (https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to add upvotes to pre-existing requests.

#### Feature Description

With the possibility of namespaces in OSS: https://twitter.com/armon/status/1419700394528186369

I was hoping the community could subscribe to this ticket to track when namespaces in OSS is available

#### Use Case(s)

I don't want to repeat the use-cases for namespaces in general but there's one specific use-case for those fully invested in the Hashistack (Terraform, Nomad, Vault and Consul)

You see, for segregation using OSS versions of the Hashistack, service key prefixes and ACLs is the hack we typically use.

Now, prefixes at least work in OSS Consul, but they don't in nomad afaik, which really requires namespaces.

So while Nomad OSS has namespaces, the other parts in the stack lock namespaces to ENT.

Which causes severe stress, confusion and occasional tears and binge drinking.

To cut to the chase, can we, please, have namespace parity in OSS Consul, atleast in line with Nomad OSS?

Start by searching existing issues for namespace feature requests and reviewing the linked context about namespaces in OSS. Done means an agreed approach is available for bringing namespace parity to OSS Consul, with the relevant use cases addressed.

Written by the indexing model from the issue text.