Add cluster fulfillment architecture documentation #17
+318
−0
Conversation
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
This document provides a complete description of how cluster fulfillment works in the OSAC architecture, including: - Fulfillment Service cluster API endpoints and data models - Management cluster scheduling and ClusterOrder creation - OSAC Controller reconciliation and webhook triggering - Ansible Automation Platform EDA integration and provisioning workflow - Cluster templates and worker node provisioning options - Infrastructure components and status tracking - Cluster deletion, scalability, and customization options The documentation integrates with the existing architecture document and provides specific file references from the fulfillment-service, cloudkit-controller, and cloudkit-aap repositories. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
schwesig
reviewed
Nov 13, 2025
| 4. **HostedCluster Monitoring**: After the webhook is triggered, the controller watches for a HostedCluster resource (created by the Ansible automation) and monitors its conditions: | ||
| - Waits for the control plane to become available | ||
| - Monitors that the cluster is not degraded | ||
| - Tracks node pool readiness |
There was a problem hiding this comment.
I am maybe reading this wrong (maybe language issue on my side), but I see here a bit of inconsistency:
In the earlier description of the Ansible workflow it sounds like Ansible is maybe creating the NodePool by itself. This is okay, but the doc should say more clear who is creating the NodePools (template or the service).
Right now it reads like the controller is waiting for a HostedCluster and the NodePools to already be there, but earlier in the document it sounds like AAP will create them during the workflow. For me this is not matching together so good.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This document provides a complete description of how cluster fulfillment works in the OSAC architecture, including:
The documentation integrates with the existing architecture document and provides specific file references from the fulfillment-service, cloudkit-controller, and cloudkit-aap repositories.
🤖 Generated with Claude Code