Conversation
Workloads whose name, placement and location together pass 63 characters never start, and customers get no error. The limit sits around 40 characters and moves with the location. Key changes: - Name every internal object with a readable workload prefix plus a fixed-length hash of the workload ID, placement and location - Validate workload names as 63-character DNS labels at create time - Report instance creation failures in workload status - Migrate the 18 production deployments make-before-break Related to #367
scotwells
marked this pull request as ready for review
September 25, 2026 18:11
ecv
previously approved these changes
Sep 25, 2026
Replace the make-before-break migration with a one-time recreate of edge compute resources, since compute will carry no compatibility code for the old names. Key changes: - Keep ordinals at the end of instance names and read them from a label - Drop the migration open question
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
2 participants
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
Workloads with long names never start, and customers get no error explaining why. The limit is around 40 characters today and shifts with the location a workload lands in.
This proposes naming every internal object the same way, with a readable piece of the workload name plus a fixed-length hash, and keeping instance numbers at the end. Any valid name up to 63 characters then runs everywhere, and two workloads can never collide.
It also adds create-time name validation and failure reasons in workload status, and replaces old names by recreating edge compute resources once rather than migrating them.
Test plan
Related to #367