Skip to content

feat(web): protect Canary relationships and support mutable referenced services - #108

Open
primowenjoy wants to merge 3 commits into
modelsphere:release-canaryfrom
primowenjoy:feat/canary-llmservice-target-pr
Open

primowenjoy wants to merge 3 commits into
modelsphere:release-canaryfrom
primowenjoy:feat/canary-llmservice-target-pr

Conversation

@primowenjoy

@primowenjoy primowenjoy commented Oct 29, 2026 •

Copy link
Copy Markdown

What type of PR is this?

  • feature
  • bug fix
  • cleanup / refactor

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 follow source.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

  • Public Console: typecheck, 70 test files / 649 tests, production build.
  • Integrated private build on current plugin main: typecheck, 88 files / 770 tests, production build.
  • Regression tests cover verified mutable references, malformed assignment locks, inherited SLO rendering and existing production binding protection.
  • Coordinated CPU mock validation used independent namespaces, no autoscaling and at most four model replicas. All 1,806 streaming requests succeeded; SLO changes followed production, and production continued serving after cleanup.

Checks

  • Web typecheck, tests and production build
  • Behavior documented in docs/console-design.md
  • No internal hostnames, IPs, registries or credentials added
  • Go and chart files are unchanged.

Notes for reviewers

This PR targets the existing release-canary base. The new commit is additive to the previously reviewed generic relationship/extension changes. Start with service-relationship.ts, InferenceDetail, SLOCard and the source metadata types. UI policy remains independent of optional Kubernetes admission. Older Swiss responses preserve existing defaults.

Release note

action required: Canary pages use a separately built optional distribution. Matching Swiss metadata can opt verified referenced services into full upgrades and expose effective inherited SLO requirements; enable mutable references only after the matching Operator, Swiss, API backend and Console are deployed.

@primowenjoy primowenjoy changed the title feat(web): support LLMService Canary targets feat(canary): support LLMService targets and protect experiment arms Oct 29, 2026
@primowenjoy primowenjoy changed the title feat(canary): support LLMService targets and protect experiment arms feat(canary): compare existing LLMServices and protect assigned arms Nov 2, 2026
@primowenjoy primowenjoy changed the title feat(canary): compare existing LLMServices and protect assigned arms feat(web): compare existing Canary arms with model mappings Nov 2, 2026
@primowenjoy primowenjoy changed the title feat(web): compare existing Canary arms with model mappings refactor(web): replace bundled Canary UI with private extension builds Nov 3, 2026
@primowenjoy
primowenjoy force-pushed the feat/canary-llmservice-target-pr branch from 45d80f4 to aa07739 Compare November 3, 2026 05:41
@primowenjoy primowenjoy changed the title refactor(web): replace bundled Canary UI with private extension builds feat(web): isolate Canary UI and restrict assigned-arm upgrades Nov 4, 2026
@primowenjoy primowenjoy changed the title feat(web): isolate Canary UI and restrict assigned-arm upgrades feat(web): display Canary relationships with UI protection Nov 5, 2026
@primowenjoy
primowenjoy force-pushed the feat/canary-llmservice-target-pr branch from 6d49b31 to 28095b7 Compare November 9, 2026 08:54
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
primowenjoy force-pushed the feat/canary-llmservice-target-pr branch from 28095b7 to 4b6b61d Compare November 11, 2026 07:25
wenyunqing and others added 2 commits November 16, 2026 23:08
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>
@primowenjoy primowenjoy changed the title feat(web): display Canary relationships with UI protection feat(web): protect Canary relationships and support mutable referenced services Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant