Allow defining meta k/vs when Nomad registers itself in Consul

hashicorp / nomad

Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.

https://www.nomadproject.io/

Other

14.9k stars 1.95k forks source link

Allow defining meta k/vs when Nomad registers itself in Consul #19567

Open skoppe opened 10 months ago

skoppe commented 10 months ago

As part of the Consul integration Nomad servers and clients by default advertise their services to Consul.

The consul configuration for Nomad allows setting the service tags, see https://developer.hashicorp.com/nomad/docs/configuration/consul#tags.

For our use case we would like to set the service meta k/vs as well.

We use the meta for configuring our metrics scraping and right now we have to resort to registering a separate consul service just for that.

jrasell commented 10 months ago

Hi @skoppe and thanks for raising this feature request. It seems like a sensible request to add this as configuration option within the Nomad agent's Consul block.