https://github.com/mrwormhole/flux-gitops

flux babysitting my k3s ARM clusters :magic_wand:
https://github.com/mrwormhole/flux-gitops

Last synced: about 11 hours ago
JSON representation

flux babysitting my k3s ARM clusters :magic_wand:

• Host: GitHub
• URL: https://github.com/mrwormhole/flux-gitops
• Owner: mrwormhole
• Created: 2023-05-01T00:06:48.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-07-19T22:03:01.000Z (4 months ago)
• Last Synced: 2024-07-20T02:40:35.540Z (4 months ago)
• Homepage:
• Size: 197 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Flux GitOps

This repository exists to rule over my k3s clusters. After a long age of years, I finally embraced gitops way of managing my clusters. The thumb of the rule is to never trust any YAMLs on my machine and follow the best gitops practices such as pull based automation for deployments.

This repository bootstrapped via flux(`2.0.0-rc.1`) as follows;

```sh

export GITHUB_TOKEN=

flux bootstrap github \

  --components-extra=image-reflector-controller,image-automation-controller \

  --owner=my-github-username \

  --repository=my-repository \

  --branch=main \

  --path=clusters/my-cluster \

  --personal

```

Along the way, I have prepared myself to all the problems such as where to store secrets and how to test insecure YAMLs without pushing directly to the repo and waiting for flux. I have solved these problems with bitnami's sealed secrets and fluxCD toolkit.

The folder structure as follows(notice there are no dev/staging/prod because clusters are dealt separately);

```

- /clusters

-- /cluster-name

--- /namespace

```

Available clusters;

```

- falk-debby

```

**Note: If I had a billion dollar worth, I would pour every penny into flux, It has saved so much pain from my end.**