Files
Huy Pham 8062bbafb4 microvm: drop the kata-config asset (#1704)
Today, `ateom` fetches the `kata-config` asset (configuration-clh.toml)
to read only 3 values `default_memory`, `default_vcpus` and
`kernel_params`. The first 2 are redundant because (1) the values never
change and (2) ateom has the same defaults. Only `kernel_params` is
relevant for the `kata-agent`; its value also changed once in the Kata
project history.

`ateom` now owns all three values, which also allows us to tune them
specifically for Substrate.

Verified e2e with a GKE cluster.

Fixes #1693

> It's a good idea to open an issue first for discussion.

- [x] Tests pass
- [x] Appropriate changes to documentation are included in the PR
2026-09-22 00:18:59 +00:00

43 lines
1.8 KiB
Bash
Executable File

#!/usr/bin/env bash
# Copyright 2026 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Stage the assembled micro-VM asset set into the GCS snapshot bucket under
# kata-assets/, where atelet fetches it (per demos/counter/counter-microvm.yaml.tmpl).
# The GKE counterpart of stage-to-rustfs.sh. Run after assemble.sh has produced $OUT.
#
# Requires the `gcloud` CLI authenticated for the bucket's project. Env: OUT (asset
# dir, default ./bin/microvm-assets/amd64), BUCKET (default ate-snapshots),
# PROJECT_ID (optional; passed to gcloud as --project when set).
set -o errexit -o nounset -o pipefail
ROOT="$(git rev-parse --show-toplevel)"
OUT="${OUT:-${ROOT}/bin/microvm-assets/amd64}"
BUCKET="${BUCKET:-ate-snapshots}"
# Pass --project only when PROJECT_ID is set (mirrors hack/teardown.sh); otherwise
# gcloud uses its active config project. ${PROJECT_ID:+...} elides the flag entirely
# when unset (same idiom as KUBECTL_CONTEXT in hack/run-microvm-demo.sh).
echo ">> Uploading assets to gs://${BUCKET}/kata-assets/ ..."
for f in cloud-hypervisor virtiofsd vmlinux rootfs.img; do
echo " $f"
gcloud storage cp ${PROJECT_ID:+--project="${PROJECT_ID}"} "${OUT}/${f}" "gs://${BUCKET}/kata-assets/${f}"
done
echo ">> Done. Verify:"
gcloud storage ls ${PROJECT_ID:+--project="${PROJECT_ID}"} "gs://${BUCKET}/kata-assets/"