Repository navigation
Conversation
The production delivery counterpart to Full-Stack Automation with ACP: the reference design (component selection, topologies, node pools and taint scheme, single persistent /var/cpaas disk, per-cluster observability), the end-to-end delivery flow including the DR domain- switch sequencing, the acp-delivery-charts rendering workflow, plugin placement by pool layout, machine configuration order, sizing by derivation from the capacity pages, and evidence-based acceptance. Encodes decisions verified in real ACP 4.3 deliveries. Tracking: AIT-74918 under Epic AIT-74911. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The link checker strips .md/.mdx but not .markdown, so the relative link resolved to a non-existent .markdown.html route and failed the build. Reference the article by title instead; titles are searchable in this knowledge base. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The delivery charts are withdrawn: hand-orchestrating the Cluster API manifests is the product reality on ACP 4.3, and no chart tooling will be maintained for the released lines. Section 3 now points at the product pages that hold the complete manifests (global install Step 4, the DR increments, Huawei DCS "Using YAML"), and keeps only what those pages scatter or deliveries get wrong: naming as a hard requirement on both sides, credentials out of applied manifests, one manifest set per cluster, reading shared values from global via the DCS page's placeholder table, keeping the provider literals, maxSurge 0 for persistent-disk pools, the three DR increments identical on both sides, and a pre-apply checklist. Wherever a product page already states a rule, the article links instead of restating it. The sizing and archive sentences that referred to chart values or rendered output are reworded to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The product documentation this article links to adopted the acp/specs platform glossary (alauda/acp-docs#1187, alauda/immutable-infra-docs #221/#222): "traditional OS" is now "non-Alauda OS" and "bootstrap host" is "bootstrap node". Follow the same wording so a reader moving between the article and the linked pages sees one name per concept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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
1 participant
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.
The production delivery counterpart to Full-Stack Automation with ACP: reference design (component selection, two supported topologies, node-pool/taint scheme, single persistent
/var/cpaasdisk with its trade-off, per-cluster observability), the end-to-end delivery flow including the DR platform-domain sequencing, how to author the cluster manifests from the product documentation plus the delivery discipline those pages scatter, plugin placement by pool layout, machine-configuration ordering, sizing by derivation from the capacity pages (no committed numbers), and evidence-based acceptance. Encodes decisions verified in real ACP 4.3 deliveries.On ACP 4.3 the cluster manifests are hand-authored YAML — that is the product reality, so the article points at the product pages that hold the complete manifests and links rather than restates wherever a product page already states a rule.
Draft until the product-doc PRs this article links to merge: alauda/immutable-infra-docs #223/#225/#227/#229/#231 (+ release-1.0 twins), alauda/acp-docs #1188–#1201.
Tracking: AIT-74918 under Epic AIT-74911.
🤖 Generated with Claude Code