Feature Description
The README still lists OCM as a supported control plane type, but that’s outdated. OCM as a standalone type has been deprecated (see issues #528, #529, #530). Now it runs within vcluster instead, so keeping it in the list creates confusion for users who might try to use the old setup.
Proposed Solution
Update the README.md and documentation to:
- Remove OCM from the "Supported Control Plane Types" list
- Update architecture sections to exclude OCM-type references
- Add clarification that OCM functionality is available through vcluster
- Focus documentation on the 4 main types: k8s, vcluster, host, external
Want to contribute?
Additional Context
This aligns with the deprecation work already done in #528, #529, and #530. The goal is to ensure documentation reflects the current architecture where OCM runs in vcluster rather than as a standalone control plane type.
Feature Description
The README still lists OCM as a supported control plane type, but that’s outdated. OCM as a standalone type has been deprecated (see issues #528, #529, #530). Now it runs within vcluster instead, so keeping it in the list creates confusion for users who might try to use the old setup.
Proposed Solution
Update the README.md and documentation to:
Want to contribute?
Additional Context
This aligns with the deprecation work already done in #528, #529, and #530. The goal is to ensure documentation reflects the current architecture where OCM runs in vcluster rather than as a standalone control plane type.