Difficulty: Intermediate
Estimated Time: 20-40 minutes

In this scenario, we will experiment with deploying a Nomad job that uses Consul Connect in a cluster with ACLs enabled.

We will do that by:

  • Enabling and bootstrapping Consul ACLs

  • Creating Consul agent policy and token

  • Install Consul agent token

  • Creating Nomad server policy and token

  • Configure Nomad with Consul token

  • Running a Connect-enabled job

    • Creating a Connect intention
    • Running the job
    • Verifying the application is running
  • Requiring Consul authentication to run jobs

  • Running a Connect-enabled job with a token

Congratulations, you have learned how to run a Nomad Consul Connect job using an ACL-enabled consul cluster.

Visit learn.hashicorp.com/nomad for more Nomad guides.

Nomad, Consul Connect, and Consul ACLs

Step 1 of 9

Provisioning Extra Course Components

There are a few components that need to be added to the environment; we are adding them now. Please wait for the complete message and then move to the next step.

Example Output

- Fixing Journal
- Installing dnsmasq

and concluding with

- Complete! Move on to the next step.

Once you see this message, you are ready to continue.

Terminal
Nomad UI
Consul UI
CountDash UI

Creating Katacoda Scenarios

Thanks for creating Katacoda scenarios. This tab is designed to help you as an author have quick access the information you need when creating scenarios.

This tab will not be visible to users.

Here are some useful links to get you started.

Running Katacoda Workshops

If you are planning to use Katacoda for workshops, please contact [email protected] to arrange capacity.

Debugging Scenarios

Below is the response from any background scripts run or files uploaded. This stream can aid debugging scenarios.

If you still need assistance, please contact [email protected]