Skip to content

Commit 2e52483

Browse files
Wei WengWei Weng
authored andcommitted
Revert "docs: add a benefit section in the README (#294)"
This reverts commit 4161bca. Signed-off-by: Wei Weng <[email protected]>
1 parent 58dca1f commit 2e52483

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

README.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,17 +19,6 @@ For any issues, please open an issue in the [KubeFleet](https://github.com/kubef
1919

2020
* [Get started here](https://kubefleet-dev.github.io/website/docs/getting-started/kind/)
2121

22-
## Key benefits and capabilities
23-
24-
### Centralized policy-driven fleet governance
25-
KubeFleet utilizes a hub-spoke architecture that creates a single control plane for the fleet. It allows fleet administrators to apply uniform cloud native policies on every member cluster, whether they reside in public clouds, private data centers, or edge locations. This greatly simplifies governance across large, geographically distributed fleets spanning hybrid and multi-cloud environments.
26-
27-
### Progressive Rollouts with Safeguards
28-
KubeFleet provides a cloud native progressive rollout plans sequence updates across the entire fleet with health verification at each step. The application owner can pause or rollback to any previous versions when they observe failures, limiting blast radius. This keeps multi-cluster application deployments reliable and predictable spanning edge, on-premises, and cloud environments.
29-
30-
### Powerful Multi-Cluster Scheduling
31-
KubeFleet's scheduler evaluates member cluster properties, available capacity, and declarative placement policies to select optimal destinations for workloads. It supports cluster affinity and anti-affinity rules, topology spread constraints to distribute workloads across failure domains, and resource-based placement to ensure sufficient compute, memory, and storage. The scheduler continuously reconciles as fleet conditions change, automatically adapting to cluster additions, removals, or capacity shifts across edge, on-premises, and cloud environments. For more details, please refer to the [KubeFleet website](https://kubefleet.dev/docs/).
32-
3322
## Documentation
3423

3524
To learn more about KubeFleet go to the [KubeFleet documentation](https://kubefleet-dev.github.io/website/).

0 commit comments

Comments
 (0)