Skip to content

Docs: Inconsistent architecture diagrams #1301

@andrewbaxter

Description

@andrewbaxter

I'm just getting started here, I was looking for whether I could use the helm-controller specifically to manage helm releases declaratively.

https://github.com/fluxcd/helm-controller/blob/main/docs/diagrams/helm-controller-overview.png shows an arrow from "Helm Controller" to "Source Controller"

However https://fluxcd.io/flux/components/ shows an arrow in the opposite direction, from "Source Controller" to "Helm Controller"

It looks like some other arrows are also reversed (e.g. between source controller and git/docker/etc)

I assume the diagrams are showing data flow: i.e. someone pushes something to git, the data from git goes to the source controller (via pull or push), the data gets transformed by source controller and moves to helm-controller (via something - does it create HelmRelease resources?), and then from helm-controller to kubernetes itself (the resources in the chart get created). So I'd expect all the arrows to point that direction.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions