How-To Guides
Configure Workloads And Bindings
Define deployable service intent and map it safely across tenant/environment cells.
Task Outcome
You produce scoped workload intent with clear assignment coverage and no hidden blast-radius surprises.
When To Use This Guide
- Adding a new service to an existing project.
- Expanding a service to new tenants or environments.
- Refactoring assignment topology after incidents or repeated preview mismatches.
Prerequisites
- Project and environments are already configured.
- Required workload sources are available.
- Operator has binding management permissions for target project scope.
UI Route Map
- Open
Workloads and Bindings. - Verify workload catalog entries and version/source badges.
- Open binding matrix and filter target tenant/environment.
- Save assignment changes and confirm scaffold status.
- Validate with preview before release.
Step-By-Step Execution
Create or update workload definition using stable naming and namespace conventions.
Open assignment matrix and filter to one tenant/environment cell first.
Bind workload to selected cells and verify immediate state feedback.
Inspect scaffold statuses and fix failed items before broad rollout.
Expand assignment to additional cells only after first cell validation.
Run preview and verify impacted outputs match intended scope.
Capture assignment summary for release reviewer context.
Assignment Strategy Choices
- Best for new services or risky changes.
- Reduces unknown side effects by validating one cell path first.
- Use only when assignment pattern is already proven.
- Always verify per-item results after bulk action.
- Upgrade non-production cells first.
- Promote to production only after runtime evidence is stable.
- Keep changes grouped by service for selective rollback options.
- Avoid mixing unrelated service changes in one assignment cycle.
Validation Checklist
- Binding matrix changes match intended tenant/environment cells.
- No unresolved scaffold failures remain.
- Preview shows expected service-level impact only.
- Release reviewer can understand assignment intent quickly.
Common Failure Modes
- Binding appears saved but scaffold remains failed.
- Bulk bind results partially fail and hide specific cell errors.
- Scope filter not applied, causing unintended broad assignment.
- Upgrade mixed with topology change, making review harder.
Release Handoff Template
Change summary:
Target project:
Target tenant/environment cells:
Workloads added/updated:
Known risks:
Rollback preference (full/service/field):
Preview link or evidence notes: