rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updating docs to be consistent with other docs from Rancher 

Signed-off-by: Matt Farina <matt.farina@suse.com>
This commit is contained in:
Matt Farina 2022-10-03 11:40:29 -04:00
parent d0619cce31
commit fc7bd30cf1
3 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/architecture.md
View File

@ -38,8 +38,3 @@ to that cluster. After the cluster credential is established the cluster "forget
The service accounts given to the clusters only have privileges to list `BundleDeployment` in the namespace created
specifically for that cluster. It can also update the `status` subresource of `BundleDeployment` and the `status`
subresource of it's `Cluster` resource.
## Scalability
Fleet is designed to scale up to 1 million clusters. There are more details to come here on how we expect to scale
a Kubernetes, controller-based architecture to 100's of millions of objects and beyond.

2
docs/concepts.md
View File

@ -1,7 +1,7 @@
# Core Concepts
Fleet is fundamentally a set of Kubernetes custom resource definitions (CRDs) and controllers
to manage GitOps for a single Kubernetes cluster or a large-scale deployment of Kubernetes clusters. Note that Fleet is designed for mass horizontal scaling, but to date, scaling up to one million clusters has only been done in a test environment, not in production.
to manage GitOps for a single Kubernetes cluster or a large-scale deployment of Kubernetes clusters.
!!! note "Note"
For more on the naming conventions of CRDs, click [here](./troubleshooting.md#naming-conventions-for-crds).

4
docs/index.md
View File

@ -6,10 +6,8 @@
- **Cluster engine**: Fleet is a container management and deployment engine designed to offer users more control on the local cluster and constant monitoring through **GitOps**. Fleet focuses not only on the ability to scale, but it also gives users a high degree of control and visibility to monitor exactly what is installed on the cluster.
- **GitOps at scale**: Fleet can manage up to a million clusters, but it's also lightweight enough that it works well for a [single cluster](./single-cluster-install.md). Fleet's capabilities are fully realized when it's used for large-scale projects. "Large scale" can mean a lot of clusters, a lot of deployments, or a lot of teams in a single organization.
- **Deployment management**: Fleet can manage deployments from git of raw Kubernetes YAML, Helm charts, Kustomize, or any combination of the three. Regardless of the source, all resources are dynamically turned into Helm charts, and Helm is used as the engine to deploy all resources in the cluster. As a result, users have a high degree of control, consistency, and auditability.
### Configuration Management
Fleet is fundamentally a set of Kubernetes [custom resource definitions (CRDs)](https://fleet.rancher.io/concepts/) and controllers that manage GitOps for a single Kubernetes cluster or a large scale deployment of Kubernetes clusters (up to one million). It is a distributed initialization system that makes it easy to customize applications and manage HA clusters from a single point.
Fleet is fundamentally a set of Kubernetes [custom resource definitions (CRDs)](https://fleet.rancher.io/concepts/) and controllers that manage GitOps for a single Kubernetes cluster or a large scale deployment of Kubernetes clusters. It is a distributed initialization system that makes it easy to customize applications and manage HA clusters from a single point.