fluxcd
/
source-controller
mirror of https://github.com/fluxcd/source-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add semver automation motive

This commit is contained in:
stefanprodan 2020-04-09 15:28:07 +03:00
parent a9a73301dd
commit 134633266a
2 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/spec/README.md
View File

@ -24,11 +24,16 @@ source manager would make Flux and Helm Operator resilient to outbound connectiv
simplify the state machine(s) that these controllers operate. simplify the state machine(s) that these controllers operate.
Managing the source operations in a dedicated controller could enable Flux to compose the desire state of a cluster Managing the source operations in a dedicated controller could enable Flux to compose the desire state of a cluster
from multiple source. from multiple source. Furthermore, the manifests transformation process could be performed by 3rd party tools
Furthermore, the manifests transformation process could be performed by 3rd party tools
(e.g. kustomize, jk, tanka, cue run by Tekton pipelines or Kubernetes Jobs) (e.g. kustomize, jk, tanka, cue run by Tekton pipelines or Kubernetes Jobs)
that subscribe to source changes events. that subscribe to source changes events.
The source controller could enable pinning the cluster desired state to a specific Git commit or Git tag.
For teams that are using semantic versioning, the source controller could monitor the Git repository tags
and set the cluster desired state to the latest release or to a tag that matches a semver pattern.
In a similar fashion, a semver pattern could trigger Helm chart upgrades without manual intervention from users.
## Goals ## Goals
The main goal is to define a set of Kubernetes objects that cluster admins and various automated operators The main goal is to define a set of Kubernetes objects that cluster admins and various automated operators

4
docs/spec/v1alpha1/gitrepositories.md
View File

@ -18,7 +18,7 @@ type GitRepositorySpec struct {
// +optional // +optional
SecretRef *v1.LocalObjectReference `json:"secretRef,omitempty"` SecretRef *v1.LocalObjectReference `json:"secretRef,omitempty"`
// The git reference to checkout and monitor for changes. // The git reference to checkout and monitor for changes, defaults to master branch.
// +optional // +optional
Reference *GitRepositoryRef `json:"ref,omitempty"` Reference *GitRepositoryRef `json:"ref,omitempty"`
@ -28,7 +28,7 @@ type GitRepositorySpec struct {
// GitRepositoryRef defines the git ref used for pull and checkout operations // GitRepositoryRef defines the git ref used for pull and checkout operations
type GitRepositoryRef struct { type GitRepositoryRef struct {
// The git branch to checkout, defaults to ('master'). // The git branch to checkout, defaults to master.
// +optional // +optional
Branch string `json:"branch"` Branch string `json:"branch"`