Skip to content

Conversation

@tgross
Copy link
Member

@tgross tgross commented Dec 5, 2025

Many users have a requirement to run exactly one instance of a given allocation because it requires exclusive access to some cluster-wide resource, which we'll refer to here as a "singleton allocation". This is challenging to implement, so this document is intended to describe an accepted design to publish as a how-to/tutorial.

Links

Jira: https://hashicorp.atlassian.net/browse/NMD-1039
Deploy previews: https://unified-docs-frontend-preview-qx8ebllbe-hashicorp.vercel.app/nomad/docs/job-declare/strategy/singleton

Contributor checklists

Review urgency:

  • ASAP: Bug fixes, broken content, imminent releases
  • 3 days: Small changes, easy reviews
  • 1 week: Default expectation
  • Best effort: No urgency

Pull request:

  • Verify that the PR is set to merge into the correct base branch
  • Verify that all status checks passed
  • Verify that the preview environment deployed successfully
  • Add additional reviewers if they are not part of assigned groups

Content:

  • I added redirects for any moved or removed pages
  • I followed the Education style guide
  • I looked at the local or Vercel build to make sure the content rendered correctly

Reviewer checklist

  • This PR is set to merge into the correct base branch.
  • The content does not contain technical inaccuracies.
  • The content follows the Education content and style guides.
  • I have verified and tested changes to instructions for end users.

@tgross tgross added the Nomad label Dec 5, 2025
@tgross tgross changed the title Nomad: recommendations for singleton deployments Nomad: recommendations for singleton deployments [DRAFT] Dec 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Thu Dec 18 16:27:17 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Thu Dec 18 16:22:59 UTC 2025

@tgross tgross force-pushed the tgross-nomad-1039 branch from 46f2009 to 09ca115 Compare December 5, 2025 19:36
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

Broken Link Checker

No broken links found! 🎉

@tgross tgross force-pushed the tgross-nomad-1039 branch 3 times, most recently from 3e86c40 to aefaab2 Compare December 11, 2025 20:58
@tgross tgross marked this pull request as ready for review December 11, 2025 21:21
@tgross tgross requested review from a team as code owners December 11, 2025 21:21
@tgross tgross requested a review from arodd December 11, 2025 21:21
@tgross tgross changed the title Nomad: recommendations for singleton deployments [DRAFT] Nomad: recommendations for singleton deployments Dec 11, 2025
Copy link
Contributor

@aimeeu aimeeu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the great technical content! I left some style guide and presentation suggestions.

tgross and others added 2 commits December 18, 2025 11:06
Many users have a requirement to run exactly one instance of a given allocation
because it requires exclusive access to some cluster-wide resource, which we'll
refer to here as a "singleton allocation". This is challenging to implement, so
this document is intended to describe an accepted design to publish as a
how-to/tutorial.
@arodd
Copy link

arodd commented Dec 18, 2025

It looks like @aimeeu caught everything that I noticed during my review. LGTM!

@tgross tgross merged commit f12f70d into main Dec 18, 2025
15 checks passed
@tgross tgross deleted the tgross-nomad-1039 branch December 18, 2025 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants