Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consul agent removed from nomad docker image #315

Open
Zortaniac opened this issue Oct 25, 2024 · 1 comment
Open

Consul agent removed from nomad docker image #315

Zortaniac opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Zortaniac
Copy link
Contributor

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.

@nicholasjackson
Copy link
Contributor

nicholasjackson commented Dec 5, 2024

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.

Currently we have split the Nomad docker image into 4 images: https://github.com/jumppad-labs/docker-files/pkgs/container/nomad

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.

@nicholasjackson nicholasjackson added the bug Something isn't working label Dec 5, 2024
@nicholasjackson nicholasjackson self-assigned this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants