Tim Gross

> However, if multiple allocations _can_ be resident on the same node, this is where I'm stuck. My exact use case is horizontal sharding of MySQL (Vitess), where a single...

Ok, I had a chat with my colleague @pkazmierczak and here's where we landed. The reason that `per_alloc` wasn't originally intended for DHV is because in CSI the `volume.source` refers...

Docs PR: https://github.com/hashicorp/web-unified-docs/pull/1426

The jobspec doesn't differentiate between dynamic and static host volumes for volumes of `type = "host"`. This was a deliberate design decision to allow job authors to be ignorant of...

Hi @dmclf! That seems like a reasonable thing to do. I've got a draft PR up here: https://github.com/hashicorp/nomad/pull/26383 However, I have a concern that users may be relying on the...

Yeah setting `resources.memory_max = -1` is almost certainly how we'd implement https://github.com/hashicorp/nomad/issues/25939 in the jobspec. The only reason we haven't just gone ahead and done that already is there are...

Note this is documented in https://developer.hashicorp.com/nomad/docs/configuration/telemetry#prometheus_metrics > Nomad's Prometheus client retains metrics in memory unless scraped, so you should not enable this field unless you are collecting metrics via Promtheus....

Doing a bit of issue cleanup and it looks like we need to document some of these details for Windows.

Hi @maxadamo! I just verified that the [`IsValidConfig`](https://github.com/hashicorp/nomad/blob/v1.5.5/command/agent/command.go#L303-L456) doesn't just do a static config check and it does things like check the serf keyfile config exists if provided. So this...

Hi @Elpaggio! > Enabling Nomad to run tasks as gMSA accounts without exposing passwords > > Current Nomad Windows executor implementation cannot run under gMSA accounts because it requires explicit...