To keep the first feature iteration predictable, the Job controller only creates a Workload and PodGroup when the Job has a well-defined, fixed shape: .spec.parallelism is greater than 1.spec.completionMode is set to Indexed.spec.completions is equal to .spec.parallelismThe schedulingGroup is not already set on the Pod template. These conditions describe the class of Jobs that gang scheduling can reason about: each Pod has a stable identity (Indexed), the gang size is known and fixed at admission time (parallelism == completions), and no other controller has already claimed scheduling responsi
Kubernetes v1.36: Advancing Workload-Aware SchedulingI love making small 2D pixel art games, especially using tools that have some constraints. Things like Pico-8 and the Playdate SDK are simple, fun, and allow for focusing on the game idea rather than the technical minuti…
Hey all — looking for some real-world input from people running TACACS+ at scale. We’re a service provider / MSP with ~100 employees, but we manage ~30,000+ network devices (switches/routers). Most of our gear supports T…
Thank you to everyone who offered feedback on my Hacker Show post for Forkle last week. I had some fantastic input from a few of you, which I have now integrated into the game.Major & Minor Improvements:- Much easier. I …
Hey HN! I'm Zach from Adam (https://adam.new/). We're building AI agents for mechanical CAD software. We’ve built the company on two fundamental beliefs:- AI will be the primary medium for creating mechanical designs jus…
Hi HN, we’re Nick and Drew, and we’re building boxes.dev – the first cloud-only agentic dev environment (ADE) that gives every Codex and Claude Code agent its own cloud computer.We’re two engineers who previously built G…
To show you the most relevant results, we’ve omitted some entries very similar to those already shown. Repeat the search with the omitted results included.