Repository navigation
docs: discuss customer-installed Configurator software and authentication - #258
Merged
Merged
Conversation
lweberru
marked this pull request as ready for review
November 16, 2026 10:07
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 16, 2026 10:07
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.
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:
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.