Skip to content

speedup: cut the extra ~8s per sandbox on the k3s tmachine rows #5863

Open

Description

@matthewgrossman

User Story

As a contributor waiting on Branch E2E, I want sandboxes on the k3s tmachine rows to start and stop about as fast as on kind, so that each conformance test there stops costing about 8 extra seconds.

Description

The same conformance tests take about twice as long on the k3s tmachine rows as on kind, and far longer than on Docker. From the JUnit results of run 44803367985:

Test Docker kind k3s VM
credential_gating::policy_binding_rest_body_keeps_placeholder_without_rewrite 1.4 s 8.0 s 18.0 s
credential_gating::policy_binding_requires_inspection_or_opt_in 1.6 s 13.1 s 18.2 s
lifecycle::restart_stopped_sandbox 1.9 s – 18.2 s
Mean over 77 tests 5.5 s – 17.6 s

Small tests show a floor of about 16 s on k3s, compared with about 8 s on kind. The VM has 4 vCPUs and 4 GB on a 4-vCPU runner.

Find where those seconds go (image pull, pod scheduling, supervisor start, readiness polling, deletion and termination grace) and remove the parts that aren't inherent to Kubernetes.

Context

Definition of Done

  • The issue records a per-phase breakdown of one sandbox's create, ready and delete on k3s and on kind.
  • Fixes for the avoidable parts land, or follow-up issues are filed for them.
  • Branch E2E k3s conformance time per test is recorded before and after.

+++ Agent notes

  • Kind numbers come from kubernetes-e2e job 136526209209 ("<== PASS ... (Ns)" lines); k3s and Docker numbers come from the JUnit artifacts e2e-results-conformance-conformance-ubuntu-k3s-k3s and ...-ubuntu-docker-rootful-deb.
  • Look at the gateway's watch and poll intervals for Kubernetes, the pod's imagePullPolicy for the sandbox and supervisor images, terminationGracePeriodSeconds, and whether tests wait for deletion to finish.

+++

Activity

  1. added
    area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.
    topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.
    on Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions