Skip to content

docs: discuss customer-installed Configurator software and authentication - #258

Merged
lweberru merged 4 commits into
mainfrom
docs/customer-installation-concept
Nov 16, 2026
Merged

lweberru merged 4 commits into
mainfrom
docs/customer-installation-concept

Conversation

@lweberru

@lweberru lweberru commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Architecture discussion only: propose a customer-installed software profile bootstrapped in the customer's STACKIT organization. No runtime, IaC or workflow implementation/deployment is introduced.

Agreed direction: local passkeys with optional corporate SSO; optional customer MailOut enabled by default; broad functional parity with the corresponding SaaS release. Explicit target project and configurable HA/sizing are part of the installer contract. Recommended implementation is a Go CLI wrapping the same versioned OpenTofu/HCL modules as direct IaC, with narrow qualified API adapters for gaps.

The complete English/German concept covers:

  • Closed customer admission and a separate installation-bound delegated authorization model, preserving SaaS proofs and Plan/Apply boundaries. Hosting and the cloud-authority model remain discussion decisions.
  • SaaS feature parity, identity-dependent adaptations, default sending-domain/DNS/SMTP setup, notification preferences and verified customer recipient bindings.
  • Bundled capabilities/reference drafts, official live STACKIT PIM/service data through an admitted scoped catalogue reader, and the customer's independently published Application catalogue. No vendor SaaS catalogue/database dependency.
  • Project/region, HA, application/database sizing and execution capacity through interactive CLI, config files and equivalent IaC inputs, with explicit cost/impact review.
  • Signed release/compatibility manifests, externally operated installation upgrades, backups, migrations, maintenance, verification, interrupted-upgrade recovery and rollback limits.
  • Separate opt-in Accelerator/template upgrades: preserve existing orders/state/runtime tuples, require fresh Plan/Apply for workload changes, and do not reinterpret pending plans with a new engine.

The private VM runner design in #257 remains complementary and optional, not an implemented private execution path. A technical vertical slice is not acceptance of a reduced customer edition.

Validation: local links and bilingual structure checked; CLI/YAML examples match exactly; both updated Mermaid diagrams parsed and rendered locally (11 nodes/11 edges each), German rendering inspected; workflow-map freshness and whitespace checks passed. No cloud provisioning, customer email, model-service requests, release or deployment.

German concept · English concept.

@lweberru
lweberru marked this pull request as ready for review November 16, 2026 10:07
@lweberru
lweberru merged commit f4b0abe into main Nov 16, 2026
16 checks passed
@lweberru
lweberru deleted the docs/customer-installation-concept branch November 16, 2026 10:07
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