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

Add impact to Helm Operator

This commit is contained in:
Hidde Beydals 2020-04-15 12:33:12 +02:00 committed by stefanprodan
parent 0084e56971
commit 8b4432fc5c
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/spec/README.md
View File

@ -26,6 +26,7 @@ of the components using them.
The controller implementation will watch for source objects in a cluster and act on them. The controller implementation will watch for source objects in a cluster and act on them.
The actions performed by the source controller could be: The actions performed by the source controller could be:
* validate source definitions * validate source definitions
* authenticate to sources and validate authenticity * authenticate to sources and validate authenticity
* detect source changes based on update policies (semver) * detect source changes based on update policies (semver)
@ -39,6 +40,7 @@ The actions performed by the source controller could be:
## Impact to Flux ## Impact to Flux
Having a dedicated controller that manages Git repositories defined with Kubernetes custom resources would: Having a dedicated controller that manages Git repositories defined with Kubernetes custom resources would:
* simplify Flux configuration as fluxd could subscribe to Git sources in-cluster and pull the artifacts * simplify Flux configuration as fluxd could subscribe to Git sources in-cluster and pull the artifacts
automatically without manual intervention from users to reconfigure and redeploy FLux automatically without manual intervention from users to reconfigure and redeploy FLux
* improve the installation experience as users will not have to patch fluxd's deployment to inject * improve the installation experience as users will not have to patch fluxd's deployment to inject
@ -51,4 +53,13 @@ the HTTPS basic auth credentials, change the source URL or other Git and PGP rel
## Impact to Helm Operator ## Impact to Helm Operator
TODO Having a dedicated controller that manages Helm repositories and charts defined with Kubernetes custom
resources would:
* simplify the Helm Operator configuration as repository and chart definitions can be re-used across
`HelmRelease` resources (see [fluxcd/helm-operator#142](https://github.com/fluxcd/helm-operator/issues/142))
* improve the user experience as repositories requiring authentication will no longer require a
`repositories.yaml` import / file mount
* simplify the architecture of the Helm Operator as it allows the operator to work with a single
source type (`HelmChart`) and way of preparing and executing installations and/or upgrades
* allow the Helm Operator to run under a non-root user as it wouldn't need to shell out to git