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

Improve CD definition 

This commit tries to clarify that whether Fleet is a continuous
_delivery_ or _deployment_ tool is pretty much open to interpretation,
since many different definitions of both concepts exist.
This commit is contained in:
Corentin Néau 2025-05-12 17:26:12 +02:00
parent 3040eae488
commit d8a40a70ee
No known key found for this signature in database
GPG Key ID: 4E10825BFE040608
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/glossary.md
View File

@ -20,13 +20,14 @@ A cluster refers to:
* a [Kubernetes cluster](https://kubernetes.io/docs/concepts/architecture/) managed by Fleet
* a `Cluster` [resource](https://github.com/rancher/fleet/blob/main/pkg/apis/fleet.cattle.io/v1alpha1/cluster_types.go#L59) in Fleet's API, which Fleet uses to manage that Kubernetes cluster
## Continuous Delivery
## Continuous Delivery/Deployment
Continuous delivery refers to the idea of enabling software to be produced in shorter cycles, with smaller increments
going through testing and being released. It does not necessarily take deployment into account.
Definitions and distinctions between Continuous _Delivery_ and Continuous _Deployment_ greatly vary, for instance
depending on:
* whether the deployment step is included in the process, and to which environment: production or other?
* what triggers a deployment: is it a manual or automated step?
Fleet rather falls under the Continuous _Deployment_ definition, as it focuses on actually deploying software
frequently.
This much is clear, though: Fleet's goal is to make it easier to automate deployments.
## Custom Resource