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
In the spirit of #5554 it would be hugely appreciated if the namespace name that a particular job runs in could be made accessible inside it's allocations environment, ie :
NOMAD_NAMESPACE=default
Reasons for having this include changing application behaviour based on environment (think test vs. production) and tagging of logs and metrics with the namespace name in order to facilitate easier multi-tenant operations.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
In the spirit of #5554 it would be hugely appreciated if the namespace name that a particular job runs in could be made accessible inside it's allocations environment, ie :
NOMAD_NAMESPACE=default
Reasons for having this include changing application behaviour based on environment (think test vs. production) and tagging of logs and metrics with the namespace name in order to facilitate easier multi-tenant operations.
The text was updated successfully, but these errors were encountered: