The GitOps Toolkit source management component
Go to file
Sunny d551e59a06 Use Event v1 API metadata keys in notifications
Signed-off-by: Sunny <darkowlzz@protonmail.com>
2022-12-19 20:21:49 +05:30
.github/workflows darwin-amd64: setup Docker using Colima 2022-12-14 14:11:37 +00:00
api api: Deprecate field gitImplementation 2022-12-12 15:34:32 +00:00
config api: Deprecate field gitImplementation 2022-12-12 15:34:32 +00:00
controllers Use Event v1 API metadata keys in notifications 2022-12-19 20:21:49 +05:30
docs
hack
internal helm: return ErrExternal when loading index fails 2022-12-19 16:12:39 +05:30
pkg minio: use container image for tests 2022-12-14 11:56:53 +00:00
tests/fuzz
.dockerignore
.gitignore
.goreleaser.yaml
CHANGELOG.md
CODE_OF_CONDUCT.md
DCO
DEVELOPMENT.md
Dockerfile
LICENSE
MAINTAINERS
Makefile
PROJECT
README.md
go.mod Update dependencies 2022-12-16 09:50:07 +00:00
go.sum Update dependencies 2022-12-16 09:50:07 +00:00
main.go

README.md

Source controller

CII Best Practices e2e report license release

The source-controller is a Kubernetes operator, specialised in artifacts acquisition from external sources such as Git, Helm repositories and S3 buckets. The source-controller implements the source.toolkit.fluxcd.io API and is a core component of the GitOps toolkit.

overview

Features:

  • authenticates to sources (SSH, user/password, API token)
  • validates source authenticity (PGP)
  • detects source changes based on update policies (semver)
  • fetches resources on-demand and on-a-schedule
  • packages the fetched resources into a well-known format (tar.gz, yaml)
  • makes the artifacts addressable by their source identifier (sha, version, ts)
  • makes the artifacts available in-cluster to interested 3rd parties
  • notifies interested 3rd parties of source changes and availability (status conditions, events, hooks)
  • reacts to Git push and Helm chart upload events (via notification-controller)