• 1 Post
  • 6 Comments
Joined 1 year ago
cake
Cake day: August 5th, 2023

help-circle


  • I am not sure if it is best practice, but this is what I do and it might provide some inspiration:

    • Bootstrap from a private gitlab.com repository with a base ansible setup. Executed from a laptop.
    • The bootstrap setups up k8s and installs a bare bones git repository docker container based on https://codeberg.org/al13nsc13nc3/gitsrv.
    • Flux CD is installed into the bare bones git repository and k8s.
    • Flux CD is used to install Forgejo and Woodpecker CI using the bare bones git repository as the gitops source of truth.

    This has the advantage that Gitops and normal git repositories are separate. I think that a similar principle would work with docker compose instead of k8s.




  • The manifest of my Kubernetes cluster is managed in a Git repository and is automatically deployed via a GitOps tool named Flux CD. When I push changes to the repository, such as adding a new application or upgrading Docker images, the deployment occurs within a few minutes.

    This is the way.

    Although I use Flux ImageUpdateAutomation instead of Renovate Bot. Did you consider using Flux to do auto updates? Are there any downsides that made you choose Renovate Bot instead?