Skip to content

Build images at main tip for staging rollout#16

Open
nadahalli wants to merge 3 commits into
mainfrom
tejaswi/build-images-main
Open

Build images at main tip for staging rollout#16
nadahalli wants to merge 3 commits into
mainfrom
tejaswi/build-images-main

Conversation

@nadahalli

Copy link
Copy Markdown
Contributor

Empty commit on main (cf58970, includes admission control #4 and restricted-host #11). The deploy-images label builds and pushes enclave/host/config-tracker images (sha-1fe855a) to dev/stage/prod ECR and produces the PCR measurements artifact for the cap-registry update. Staging deploy: PRIV-516 / PRIV-541. Not for merge.

Empty commit: tree is identical to main (cf58970), so the EIF/PCR match a
main build. Carries the deploy-images label to build+push enclave, host and
config-tracker images for the staging rollout (PRIV-516/PRIV-541).
@nadahalli
nadahalli marked this pull request as ready for review July 23, 2026 12:45
The /memory endpoint reported only Go-runtime-mapped memory (usedMB), which
excludes native allocations, notably the wasmtime WASM linear memory that
dominates the enclave's footprint under load. Load testing showed usedMB
barely moving while the enclave approached its wedge, because the pressure
was all outside Go's accounting.

Add an additive rssMB field (VmRSS from /proc/self/status) so /memory
reflects the true resident footprint. usedMB is unchanged. rssMB is 0 on
non-Linux dev builds. Parsing is unit-tested; RSS reading changes the EIF,
so this needs a rebuild + PCR update to deploy.
@nadahalli
nadahalli requested a review from a team as a code owner July 24, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant