Repository navigation
Conversation
This was referenced Oct 31, 2026
This was referenced Oct 31, 2026
Each Kind smoke shard builds and deploys the Next.js UI during its bring-up, about 100 seconds, and the bring-up waits for every workload, so the UI is one of the two steps that end it. No smoke scenario reads the UI. SPACE_KIND_UI=0 now leaves its image and release out of the Tiltfile, and the shards set it; a local up.sh still deploys the UI.
Collaborator
Author
|
Closing: measured on Kind CI, skipping the UI did not shorten the bring-up, with or without #1020's early seed build, because |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Draft: no measured latency gain yet.
SPACE_KIND_UI=0leaves the UI's image build and release out of the Tiltfile, and the Kind smoke shards set it. No smoke scenario reads the UI. Its image build took about 100 s per shard and was one of the two steps that ended the bring-up. A localup.shstill deploys the UI.Measured effect. None on its own. Without the UI,
space-seed-publishstill ends the bring-up at about the same moment. With #1020's early seed build grafted on, in a since-closed measurement draft, the seed rootfs moved earlier: 58-129 s into the bring-up instead of insidespace-seed-publish. Butspace-seed-publishstill waits for internal-api and its own image load, and it still ended the bring-up.The difference is within run-to-run noise.
What it does save: one 100 s image build, and its CPU, per shard. It becomes worth merging when the seed publish's own path shortens.
Stack
Validation
scripts/tests/test_kind_prune_superseded_images.pypasses (63 tests), includingtest_tiltfile_builds_exactly_the_listed_images.Severity and risk
Severity: does not apply.
Risk: Kind CI no longer deploys the UI, so a change that breaks the UI's image build or chart is no longer caught by the Kind smoke. No smoke scenario exercised the UI itself. Revert to roll back.
AI assistance: Claude Code drafted the change and this description.
🤖 Generated with Claude Code