Networking

As Nomad is a workload orchestrator, it focuses on the scheduling aspects of a deployment, touching areas such as networking as little as possible. Nomad operators should make a choice of networking mode based on infrastructure requirements and organizational policies. Regardless of the chosen networking mode, it's crucial to ensure that all necessary networking configurations are present and available before deploying jobs. If there's a mistake in the networking configuration, you will encounter errors when attempting to deploy jobs.

Considerations

• For self-service models, it is ideal for application owners to have templated job definitions by Nomad operators with the correct networking mode and port mappings.
• Coordinate with your network engineers regarding any necessary security groups or firewall configurations to ensure proper network access for your workloads.
• Carefully consider your port mapping strategy. Use dynamic port allocation when possible to avoid conflicts, especially in shared environments.
• Familiarize yourself with the network plugins available in your Nomad cluster. Different plugins may offer features like network policy enforcement or advanced routing capabilities.
• If using Docker or Podman drivers, leverage their native networking capabilities, including custom overlay networks for multi-host communication.
• The Container Network Interface (CNI) plugin allows for more advanced networking configurations and is particularly useful in multi-node clusters. It enables the use of various network plugins for different networking requirements.
• For more information on networking in Nomad, refer to the Nomad networking(opens in new tab) documentation.