-
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
core: open source namespaces #9135
Conversation
74860be
to
899b88d
Compare
899b88d
to
9db8f71
Compare
e124d44
to
47b8db8
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!
There's also a namespaces E2E test that we'll want to move into OSS as well. But that can be a separate PR for sure.
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'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
The community has spoken, and HashiCorp has listened: namespaces will be open source in Nomad v1.0!
HashiCorp's goal is to have compelling enterprise offerings to fit the needs of large scale organizations. Not only are namespaces a useful cluster segmentation tool at any scale, but a lot has changed in our enterprise offering since namespaces were introduced 2 years ago in Nomad 0.7: Preemption for batch and service jobs, audit logging, licensing, and multi-region deployments have all been added to meet the needs of enterprise organizations (in addition to quotas, Sentinel, Autopilot, and other long-standing enterprise features).
The Namespace commands and API client have always been open source, so they eased the transition.