#fluxcd — Public Fediverse posts

От Flux CLI к Flux Operator и Status Page

Flux CD — это набор инструментов для GitOps в Kubernetes. Он следит за Git-репозиторием и автоматически приводит состояние кластера в соответствие с описанными в нём манифестами и Helm-чартами. Flux работает как контроллер внутри кластера: подтягивает изменения из Git, применяет их через Kubernetes API и отслеживает статус каждого ресурса. Проект является graduated-проектом CNCF. Когда вы впервые поднимаете GitOps в Kubernetes, Flux CD кажется достаточным: flux bootstrap , манифесты в Git, контроллеры тянут состояние кластера. Но лучше перейти на Flux Operator:

https://habr.com/ru/articles/1030980/

#Flux_CD #Flux_Operator #FluxInstance #GitOps #Kubernetes #FluxReport #FluxCD #IaC #infrastructure_as_code

От Flux CLI к Flux Operator и Status Page

Flux CD — это набор инструментов для GitOps в Kubernetes. Он следит за Git-репозиторием и автоматически приводит состояние кластера в соответствие с описанными в нём манифестами и Helm-чартами. Flux работает как контроллер внутри кластера: подтягивает изменения из Git, применяет их через Kubernetes API и отслеживает статус каждого ресурса. Проект является graduated-проектом CNCF. Когда вы впервые поднимаете GitOps в Kubernetes, Flux CD кажется достаточным: flux bootstrap , манифесты в Git, контроллеры тянут состояние кластера. Но лучше перейти на Flux Operator:

https://habr.com/ru/articles/1030980/

#Flux_CD #Flux_Operator #FluxInstance #GitOps #Kubernetes #FluxReport #FluxCD #IaC #infrastructure_as_code

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

Nu e heimelaben min: to ~10år gamle stasjonær-PCa me #nixOS, tilkobla UPS, én gammel laptop me Bazzite, og én vps nedi oslo me nixOS.
De kjøra alle kubernetes i form av #k3s, som holdes i tøylan av #fluxcd.
nixOS tøyleholdes av #comin.

Kikk gjerne: https://codeberg.org/papiris/infra-cd og /nix-config

Neste bi å få opp monitorering så æ kan hold beire øye me krætturet, og offsite backup av nåkka slag.
Rop ut om du vil bi me på å lag ei gjensidig lagringsklynga basert på sjøldrifta S3: https://garagehq.deuxfleurs.fr

Nu e heimelaben min: to ~10år gamle stasjonær-PCa me #nixOS, tilkobla UPS, én gammel laptop me Bazzite, og én vps nedi oslo me nixOS.
De kjøra alle kubernetes i form av #k3s, som holdes i tøylan av #fluxcd.
nixOS tøyleholdes av #comin.

Kikk gjerne: https://codeberg.org/papiris/infra-cd og /nix-config

Neste bi å få opp monitorering så æ kan hold beire øye me krætturet, og offsite backup av nåkka slag.
Rop ut om du vil bi me på å lag ei gjensidig lagringsklynga basert på sjøldrifta S3: https://garagehq.deuxfleurs.fr

Nu e heimelaben min: to ~10år gamle stasjonær-PCa me #nixOS, tilkobla UPS, én gammel laptop me Bazzite, og én vps nedi oslo me nixOS.
De kjøra alle kubernetes i form av #k3s, som holdes i tøylan av #fluxcd.
nixOS tøyleholdes av #comin.

Kikk gjerne: https://codeberg.org/papiris/infra-cd og /nix-config

Neste bi å få opp monitorering så æ kan hold beire øye me krætturet, og offsite backup av nåkka slag.
Rop ut om du vil bi me på å lag ei gjensidig lagringsklynga basert på sjøldrifta S3: https://garagehq.deuxfleurs.fr

Spent a little time this weekend getting to know Tekton

People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.

So far, all I've really done is gone over some of the examples:

https://tekton.dev/docs/getting-started/

Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.

Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.

Anyone have any interesting use cases for Tekton in their own work/home?

#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted

Spent a little time this weekend getting to know Tekton

People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.

So far, all I've really done is gone over some of the examples:

https://tekton.dev/docs/getting-started/

Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.

Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.

Anyone have any interesting use cases for Tekton in their own work/home?

#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted

Spent a little time this weekend getting to know Tekton

People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.

So far, all I've really done is gone over some of the examples:

https://tekton.dev/docs/getting-started/

Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.

Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.

Anyone have any interesting use cases for Tekton in their own work/home?

#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted

Spent a little time this weekend getting to know Tekton

People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.

So far, all I've really done is gone over some of the examples:

https://tekton.dev/docs/getting-started/

Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.

Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.

Anyone have any interesting use cases for Tekton in their own work/home?

#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted

Spent a little time this weekend getting to know Tekton

People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.

So far, all I've really done is gone over some of the examples:

https://tekton.dev/docs/getting-started/

Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.

Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.

Anyone have any interesting use cases for Tekton in their own work/home?

#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted

Flux monorepo layout

Flux, or FluxCD, is a "set of continuous and progressive delivery solutions for Kubernetes that are open and extensible" and is my preferred way to do "GitOps" in my Kubernetes clusters. I like Flux because it handles Helm extremely well (I'm a big fan of Helm) and allows me to have a simple fallback if something goes wrong. In this post, I will go through the process of

https://dustinrue.com/2025/03/flux-monorepo-layout/

#colima #fluxcd #helm #k9s #Kubernetes

Flux monorepo layout

Flux, or FluxCD, is a “set of continuous and progressive delivery solutions for Kubernetes that are open and extensible” and is my preferred way to do “GitOps” in my Kubernetes clusters. I like Flux because it handles Helm extremely well (I’m a big fan of Helm) and allows me to have a simple fallback if something goes wrong. In this post, I will go through the process of installing flux, k3s that can be used for testing and then creating a Flux project that adopts Flux’s documented monorepo design. I have also published a copy of the work detailed here to Github so you can use as a working starter for your own project.

[…]

https://dustinrue.com/2025/03/flux-monorepo-layout/

#colima #fluxcd #helm #k9s #Kubernetes

Learned about #KCL today at work, gives me data oriented golang-vibes.
I will probably move my #homelab to it, as it nicely integrates with #fluxcd. Should be easy and no more 'generic' helm charts!

Managed to migrate my first #Truecharts app from #TrueNAS to #Talos.

Do this only if you need another hobby. It is definitely nothing like the comfort the TrueNAS App Catalogue and UI provided.

But i like #Kubernetes and so it is fine for me, to play around with #CertManager, #RenovateBot, #FluxCD and #VolSync. Just have to compare resource consumption now 😅

🚀 @fluxcd & `HelmRelease`: A powerful combo, but can be even better!

A guide explores #kustomize for a more streamlined, auditable GitOps workflow. 🕵️

https://link.davinkevin.fr/flux-and-helmrelease

#FluxCD #Kustomize #Helm #DevOps @kubernetesio

Low hanging stateless fruits moved from ArgoCD to #FluxCD: #CertManager, #ExternalDNS, #Drone, #Stakater #Reloader. Those seem to be in working order. It's gonna take a bit of time moving the stateful projects though.

@fyw321 @geerlingguy My 8 node cluster costs around 55W via POE. It is 3 pi4 8G control+worker nodes, and 5 pi4 4G worker-only nodes (1 is actually 8G.)

Storage is #iscsi on spinning rust on #TrueNAS, but you can do all this on local disks.

It handles a LOT:
- #Promstack, #FluxCD, #Calico, various scrapers
- #Adguard
- #Blocky (another adblocking #dns)
- #Jellyfin
- #Ombi, Prowlarr, *arr, Deluge
- Home automation helpers (#ser2sock instances, #zigbee/#zwave 2mqtt, but not HA itself)
- #Argo for builds (deprecated in favor of the x64 cloud lab. Building x64 docker containers on arm is BAD)
- Democratic CSI for iscsi/nfs
- #GoHarbor container registry & #dockerhub cache
- #Mealie recipe manager
- #Monica contact manager
- #SMTP relay to gmail
- #Ubiquiti console (bootstrapping becomes a chicken and egg problem though, if it goes down wrong)
- #Wireguard #VPN server
- #Whoogle
- #VisualStudioCode and a #dind sidecar
- SSL termination for most of the rest of the network