Repository navigation
feat(web): protect Canary relationships and support mutable referenced services - #108
Open
primowenjoy wants to merge 3 commits into
Open
primowenjoy wants to merge 3 commits into
primowenjoy wants to merge 3 commits into
Conversation
primowenjoy
force-pushed
the
feat/canary-llmservice-target-pr
branch
from
November 3, 2026 05:41
45d80f4 to
aa07739
Compare
primowenjoy
force-pushed
the
feat/canary-llmservice-target-pr
branch
from
November 9, 2026 08:54
6d49b31 to
28095b7
Compare
Keep the optional Canary distribution separate while protecting referenced service lifecycle actions in Console. Preserve production route bindings during upgrades and expose independent autoscaling controls. Fixes modelsphere#124
primowenjoy
force-pushed
the
feat/canary-llmservice-target-pr
branch
from
November 11, 2026 07:25
28095b7 to
4b6b61d
Compare
In compact list mode, standalone services no longer get a service-relationship badge; services with ownership keep the ownership row, and the badge itself only when there is no owner. Detail pages keep the previous display. Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
What type of PR is this?
What this PR does and why
Keep the optional Canary frontend outside public Console while retaining generic extension hooks, relationship displays and UI lifecycle protection. Public builds have an empty extension registry; private builds reuse the host login, permissions, translations, theme and query state.
Verified referenced arms use the full upgrade form when Swiss exposes
assignedTo.mutable; older responses retain adaptive-only upgrades. Unverified references remain locked, owned services remain parent-managed and referenced-service uninstall stays blocked. Production upgrades continue to preserve their chart and routing/Service binding, including YAML changes. Autoscaling remains independently configurable from SLO requirements.SLO views follow the server's effective
source: inherited production requirements remain visible, inherited editors followsource.canEdit, and independent arm SLOs remain editable. This supports resizing and SLO edits during resource-constrained existing-service experiments.Which issue(s) this PR fixes
Fixes #124.
Coordinates Swiss #68 and Operator #13. Matching API backend: Canary plugin #10.
How it was tested
Checks
docs/console-design.mdNotes for reviewers
This PR targets the existing
release-canarybase. The new commit is additive to the previously reviewed generic relationship/extension changes. Start withservice-relationship.ts,InferenceDetail,SLOCardand the source metadata types. UI policy remains independent of optional Kubernetes admission. Older Swiss responses preserve existing defaults.Release note