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:
parent
3040eae488
commit
d8a40a70ee
|
|
@ -20,13 +20,14 @@ A cluster refers to:
|
||||||
* a [Kubernetes cluster](https://kubernetes.io/docs/concepts/architecture/) managed by Fleet
|
* 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
|
* 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
|
Definitions and distinctions between Continuous _Delivery_ and Continuous _Deployment_ greatly vary, for instance
|
||||||
going through testing and being released. It does not necessarily take deployment into account.
|
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
|
This much is clear, though: Fleet's goal is to make it easier to automate deployments.
|
||||||
frequently.
|
|
||||||
|
|
||||||
## Custom Resource
|
## Custom Resource
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue