Re:Homebrew to deprecate and add caveat for HashiCorp
by jen20 on Monday October 09, 2023 @12:22PM
(#37822000)
Nomad has equivalent mechanisms for collecting logs to Kubernetes. None are built in, in either platform.
Re:Homebrew to deprecate and add caveat for HashiCorp
by nanmu42 on Wednesday October 11, 2023 @05:18AM
(#37842431)
Would you like to provide a link? It would help me a lot. Thanks.
Re:Homebrew to deprecate and add caveat for HashiCorp
by jen20 on Wednesday October 11, 2023 @05:06PM
(#37850263)
https://developer.hashicorp.com/nomad/docs/job-specification... covers much of it from the collection side
Re:Homebrew to deprecate and add caveat for HashiCorp
by nanmu42 on Tuesday October 10, 2023 @12:07AM
(#37828420)
Yes k8s does not provide a out-of-box logging collection solution but since everything is in containers, we can piggyback on Docker or Containerd via deamonset to get all the logs.
Nomad on the other hand support various payload(native exec, exec via chroot, containers, even Firecracker VM by community support), so doing logging collection by end users is trickier. It worth noting that Nomad UI(a official web admin panel) has log tailing utility built-in so maybe partial work has already been done. The developers may have other concerns.
The related issue is https://github.com/hashicorp/nomad/issues/10220
Having read the sibling's comment, I think I better understand the situation since Nomad isn't a container orchestrator and thus there isn't one homogeneous place from which _to_ collect the logs, but in any sane k8s setup that's not true since both dockerd and containerd have mechanisms to influence that behavior and k8s is perfectly able, and supports, scheduling per-Node utility plumbing stuff like that without drama