You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We noticed that consul was recently removed from the nomad docker image used for the nomad cluster nodes. This is now breaking our environment.
Since it is advised to have a dedicated consul agent for each node and the configuration is still containing the consul_config key.
We are wondering if it was intentional or a side-effect of migrating to a new repository for the image build?
To Reproduce
Run a nomad cluster with a consul configuration pointing to localhost.
Expected behavior
A consul agent should start as part of each nomad node.
The text was updated successfully, but these errors were encountered:
Hey, we are working on some updates to this as we want to decouple Nomad from Consul. Nomad now has built in service discovery and secrets management. While this does not provide service mesh capabilities it is a step forward where basic Nomad use is far simpler.
This has reduced the size of the base image by 50% from 1.3GB to about 650MB, there are still Nomad images specifically for Qemu, Java, Consul, and a build containing everything but the intention is that any specific Consul functionality such as the config files will be removed from the Nomad cluster.
We have always preferred running Consul agent as a system job on top of Nomad as enables the core VM to be far simpler and makes the upgrade path for Consul simpler too. To help with this pattern we are currently working on a Jumppad module that will allow you to install Consul onto a Nomad cluster and will also allow the configuration of various TLS and ACL options. This will be detailed along with the new images in the documentation and we hope to have this work done by the weekend.
While the consul_agent config will be deprecated in the next release you will be able to use one of the older images by setting the image parameter on the cluster, this overrides the default image. Previous images t hat contain Consul can be found here:https://hub.docker.com/repository/docker/shipyardrun/nomad/general
Sorry if this causes any inconvenience, we are trying to make Jumppad simpler and easier to maintain.
Describe the bug
We noticed that consul was recently removed from the nomad docker image used for the nomad cluster nodes. This is now breaking our environment.
Since it is advised to have a dedicated consul agent for each node and the configuration is still containing the
consul_config
key.We are wondering if it was intentional or a side-effect of migrating to a new repository for the image build?
To Reproduce
Run a nomad cluster with a consul configuration pointing to localhost.
Expected behavior
A consul agent should start as part of each nomad node.
The text was updated successfully, but these errors were encountered: