-
Notifications
You must be signed in to change notification settings - Fork 2k
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
client: expose network namespace CNI config as task env vars. #11810
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach here seems technically sound. We have an existing set of NOMAD_IP
, etc. variables described in the network
docs... how do we envision these interacting?
iirc these represent the host assignments when running in |
5830f28
to
0a89baa
Compare
I've just tested this in a CNI network using calico. It works great and saved a bunch of hassle modding container images to autodetect their IP. Thanks @jrasell. |
f866228
to
7b9e54c
Compare
Ember Test Audit comparison
|
This change exposes CNI configuration details of a network namespace as environment variables. This allows a task to use these value to configure itself; a potential use case is to run a Raft application binding to IP and Port details configured using the bridge network mode.
7b9e54c
to
1282575
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I forgot I had this stashed locally. Raising it initially as a draft PR
to get early feedback and will modify and add docs etc at a later
date.
This change exposes CNI configuration details of a network
namespace as environment variables. This allows a task to use
these value to configure itself; a potential use case is to run
a Raft application binding to IP and Port details configured using
the bridge network mode.