flux-get-started

Testing from container

We published a step-by-step run-through on how to use Flux and Helm Operator over here.

Workloads

Kubernetes deployment, ClusterIP service and Horizontal Pod Autoscaler
init container automated image updates (regular expression filter)
container automated image updates (semantic versioning filter)

Helm Releases

Mongodb

Source: Helm repository (stable)
Kubernetes deployment
automated image updates (semantic versioning filter)

Redis

Source: Helm repository (stable)
Kubernetes stateful set
locked automated image updates (semantic versioning filter)

Ghost

Source: Git repository
disabled automated image updates (glob filter)
has external dependency - mariadb (stable)

Manifests Validation

CircleCI jobs:

validate Kubernetes manifests with kubeval
validate Flux Helm Releases with hrval

Getting Help

If you have any questions about, feedback for or problems with flux-get-started:

Invite yourself to the CNCF community slack and ask a question on the #flux channel.
To be part of the conversation about Flux's development, join the flux-dev mailing list.
File an issue.

Your feedback is always welcome!

flux-get-started-test