Nomad vs Kubernetes: source lines of code compared

The Nomad vs Kubernetes comparison on OctoCounts shows side-by-side source line counts for hashicorp/nomad and kubernetes/kubernetes, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of hashicorp/nomad and kubernetes/kubernetes using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-16, hashicorp/nomad contains 836,866 total lines (629,319 code) across 3,820 files, while kubernetes/kubernetes contains 4,975,906 total lines (4,005,126 code) across 15,218 files as of 2026-11-16. kubernetes/kubernetes has about 6.4x the counted code lines of hashicorp/nomad under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metrichashicorp/nomadkubernetes/kubernetes
Files3,82015,218
Total lines836,8664,975,906
Code lines629,3194,005,126
Comment lines89,925657,264
Blank lines117,622313,516
Languages counted2317

Top languages in hashicorp/nomad: Go (85.3% of code), JavaScript (5.5% of code), Handlebars (2.9% of code). Top languages in kubernetes/kubernetes: Go (66.5% of code), JSON (25.7% of code), YAML (6.4% of code). Go, YAML appear in both top language lists; JavaScript, Handlebars, HCL appear only in hashicorp/nomad's top languages; JSON, Shell, PO File appear only in kubernetes/kubernetes's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. hashicorp/nomad was counted at ref main (commit 359056d76692) on 2026-11-16; kubernetes/kubernetes was counted at ref master (commit 954517dcb5c7) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. hashicorp/nomad: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. kubernetes/kubernetes: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: hashicorp/nomad contains Nomad: HashiCorp's cluster scheduler and workload orchestrator, implemented in Go as a single-binary server/agent system with its UI and tests. kubernetes/kubernetes is the Kubernetes core monorepo: API server, scheduler, kubelet, controllers, client libraries, generated code, and tests. Both are Go orchestration systems, but at markedly different repository scopes, counted on the dates shown above.

Nomad's counted tree includes its web UI and agent code alongside the scheduler, while Kubernetes's tree aggregates components that are deployed and versioned together — different packaging philosophies are visible in the totals.

The much larger Kubernetes count should not be read as superiority or as Nomad being incomplete: the two systems make different scope and packaging trade-offs, and orchestrator choice depends on workload requirements, not repository size.

Sources: hashicorp/nomad repository · kubernetes/kubernetes repository (core monorepo). Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, hashicorp/nomad or kubernetes/kubernetes?

As of 2026-11-16, hashicorp/nomad contains 836,866 total lines (629,319 code) across 3,820 files, while kubernetes/kubernetes contains 4,975,906 total lines (4,005,126 code) across 15,218 files as of 2026-11-16. kubernetes/kubernetes has about 6.4x the counted code lines of hashicorp/nomad under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for hashicorp/nomad, kubernetes/kubernetes, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. hashicorp/nomad was counted at ref main (commit 359056d76692) on 2026-11-16; kubernetes/kubernetes was counted at ref master (commit 954517dcb5c7) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.