Add MCO overview docs page #51
Conversation
| **Release Target:** The project is starting a public preview in mid-late April | ||
| 2025. Partners interested in collaborting can email [email protected] for | ||
| more information. | ||
| **Release Target:** The project is currently available as an early public |
There was a problem hiding this comment.
let's remove mention of release and all given we don't provide a date. Let's just state what is out there available.
There was a problem hiding this comment.
I think we should make it clear that the plan is for it to be open source. How about "The project is currently available as an early public preview. An initial open source beta release is planned for later in 2025."?
There was a problem hiding this comment.
I think we should be specific about what is available to manage expectations as there's no formal definition for public previews.
Same for what is planned to be open source (e.g. placement API, mco controller). The MCO overview mentions other components that will not be oss (e.g. cp syncer).
| # Overview of Multi-Cluster Orchestrator | ||
|
|
||
| Multi-Cluster Orchestrator (MCO) dynamically schedules an application’s | ||
| multi-cluster and multi-region deployment, allowing the application to |
There was a problem hiding this comment.
multi-region is technically cluster dependent.
There was a problem hiding this comment.
Right. I think people will understand what we mean, but if you think it's unclear I'm open to suggestions
| run the workload and which clusters/regions are more desirable to use | ||
| * Information about region capacity, such as which regions currently have | ||
| certain machine types available | ||
| * Current load on the application |
There was a problem hiding this comment.
technically this is only if they have an HPA.... which we quite require. but mco itself doesn't look at load?
There was a problem hiding this comment.
Right, this is a simplification but I think it's worth including as part of the conceptual framework. Technically the previous one is a simplification too since we don't actually know when machines are available, only when they're unavailable.
Co-authored-by: Andrew Peabody <[email protected]> Signed-off-by: Owen Strain <[email protected]>
Co-authored-by: Andrew Peabody <[email protected]> Signed-off-by: Owen Strain <[email protected]>
Co-authored-by: Andrew Peabody <[email protected]> Signed-off-by: Owen Strain <[email protected]>
Co-authored-by: Andrew Peabody <[email protected]> Signed-off-by: Owen Strain <[email protected]>
Signed-off-by: Owen Strain <[email protected]>
Signed-off-by: Owen Strain <[email protected]>
Signed-off-by: Andrew Peabody <[email protected]>
4 participants
No description provided.