Skip to content

installer: adopt ate-setup's Go micro-VM staging (core #2092) before re-pinning past v1.0.0-rc.1 #99

Closed

Description

@MushuEE

Core agent-substrate/substrate#2092 (merged 2026-10-30 on main) ported the micro-VM dependency setup from shell to Go and deleted hack/install-microvm-deps.sh and hack/microvm-assets/. It is not in release-1.0 or v1.0.0-rc.1, so the current pin (f86fde9) is unaffected. The installer's micro-VM step breaks on the first re-pin to a core commit that includes #2092.

What changed in core

  • ate-setup deploy ate-system and deploy sandboxconfig now assemble, stage, and apply the microvm SandboxConfig themselves. New flag --sandbox-classes (default gvisor,microvm); --sandbox-classes=gvisor skips micro-VM staging.
  • On non-kind clusters it uploads with gcloud to gs://<BUCKET_NAME>-assets (still the bucket tools/setup-gcp creates) and stages both amd64 and arm64.
  • Layout changed from kata-assets/ to content-addressed microvm-assets/<arch>/<sha256>. The template moved to manifests/ate-install/sandboxconfig-microvm.yaml.tmpl.
  • delete ate-system releases SandboxConfig finalizers before CRD teardown.

What needs to change here (at the re-pin past #2092)

  • installer/internal/snapshot/snapshot.go InstallMicroVMDeps: drop the hack/install-microvm-deps.sh --install step. Micro-VM installs rely on deploy ate-system (default classes); gVisor-only installs pass --sandbox-classes=gvisor so ate-setup doesn't require gcloud or the asset bucket.
  • installer/internal/steps/steps.go MicroVMDeps: progress phases key off the old script's output (Uploading assets to gs://); re-key them to ate-setup's output or fold them into the Deploy tracker.
  • Dry-run SimLines: remove the kata-assets/ path (also fixes the missing -assets suffix).
  • --upgrade: re-stage micro-VM assets with go run ./cmd/ate-setup deploy sandboxconfig. Assets are content-addressed now, so this is safe to run on every upgrade.
  • doctor.go: re-check host-tool requirements (sha256sum/zstd/unzip/jq/make were for the shell path).
  • README (lines ~133, ~200–207): replace the hack/install-microvm-deps.sh --install/--delete instructions and the kata-assets/ description.
  • Clusters staged by older pins keep assets under kata-assets/; they're inert after the new SandboxConfig is applied. Document that, or clean them up.

Keep the existing fallback for old trees (hack/install-ate.sh) as is.

Related: #82 (setup-gcp migration umbrella), #94 (rc.1 re-pin), #50, agent-substrate/substrate#3505 (removes core's tools/setup-gcp).

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions