Skip to content

Add NoOpDeployer for infrastructure-free local runs#73

Merged
pradeepvrd merged 1 commit into
gke-labs:mainfrom
adrianchung:add-noop-deployer
Jun 18, 2026
Merged

Add NoOpDeployer for infrastructure-free local runs#73
pradeepvrd merged 1 commit into
gke-labs:mainfrom
adrianchung:add-noop-deployer

Conversation

@adrianchung

@adrianchung adrianchung commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds a NoOpDeployer (activated by BENCH_NO_INFRA=true) that skips tofu/GCP cluster provisioning, so the benchmark pipeline can run without infrastructure — useful for testing provider adapters and the evaluator locally. Takes precedence over any task-level infrastructure config. Includes unit tests.

Scope

  • deployers/factory.pyNoOpDeployer + BENCH_NO_INFRA handling
  • tests/test_factory.py — unit tests

Adds a NoOpDeployer to deployers/factory.py, activated by BENCH_NO_INFRA=true,
which skips tofu/GCP cluster provisioning so the benchmark pipeline can run
without infrastructure (e.g. when testing provider adapters locally). Takes
precedence over any task-level infrastructure config. Includes unit tests in
tests/test_factory.py.
Comment thread deployers/factory.py
"name": self._cluster_name,
"location": "local",
"project": self._project_id,
"kubeconfig_path": os.environ.get("KUBECONFIG", ""),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

We should fallback to ~/.kube/config since not all clients might have fallback implemented.

@pradeepvrd pradeepvrd merged commit 63315a6 into gke-labs:main Jun 18, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants