home.social

#fluxcd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fluxcd, aggregated by home.social.

  1. От 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:

    habr.com/ru/articles/1030980/

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

  2. От 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:

    habr.com/ru/articles/1030980/

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

  3. От 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:

    habr.com/ru/articles/1030980/

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

  4. От 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:

    habr.com/ru/articles/1030980/

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

  5. The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with , , , and .

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

    Prepare for your DevOps exam with free LPI Learning Materials!

  6. 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: lpi.org/tb0t

    Prepare for your DevOps exam with free LPI Learning Materials!

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

  7. 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: lpi.org/tb0t

    Prepare for your DevOps exam with free LPI Learning Materials!

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

  8. 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: lpi.org/tb0t

    Prepare for your DevOps exam with free LPI Learning Materials!

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

  9. 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: lpi.org/tb0t

    Prepare for your DevOps exam with free LPI Learning Materials!

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

  10. My FluxCD notifications used to go through a Matrix server, but that felt like too much infrastructure for just a few alerts.

    Then @simonbs's Brrr app came along - simple push notifications without running a server. Just one issue: FluxCD's webhook format doesn't match what Brrr expects.

    So I built Let-It-Brrr - a tiny service that translates the payloads. Now deployments and config changes pop up right on my lock screen ✨

    github.com/ThisIsBenny/Let-It-

    #homelab #fluxcd #selfhosted

  11. Taming CRM releases in a regulated FinTech environment

    EXANTE, a licensed international broker, recently delved into how it overhauled its delivery process for a business-critical CRM…
    #Environment #Celery #changemanagement #ComplianceAutomation #DevOps #Exante #fintech #FluxCD #GitLab #Jenkins #Jira #Kubernetes #PostgreSQL #Redis #regtech #slack
    europesays.com/2842666/

  12. I recently migrated my homelab's GitOps repo from github to my forgejo instance and it is so satisfying not relying on github for my cluster any more.

    #homelab #GitOps #fluxcd #selfhosted

  13. 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: 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: garagehq.deuxfleurs.fr

  14. 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: 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: garagehq.deuxfleurs.fr

  15. 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: 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: garagehq.deuxfleurs.fr

  16. New blog post on how we manage env variables to configure our applications in Kubernetes, to allow changing them without a redeploy:

    wouterj.nl/2026/02/manage-env-

    #kubernetes #FluxCD

  17. is _the_ most under-delivering tool (compared to its marketing claims) which i have been "forced" to work with in recent times.

    today

    - it made it super hard to spot my own error where i had a string in a yaml instead of a []string
    - i found out that it had never reported three warnings which helm did report
    - failed to re-deploy automatically after a manual delete deployment …

    this tool has caused me so much frustration that i am really prejudiced now.

  18. Helm-controller with a memory request of 64Mi feels so naive lol

    Yes it works until the node gets any form of memory pressure. #kubernetes #fluxCd

  19. 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:

    tekton.dev/docs/getting-starte

    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

  20. 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:

    tekton.dev/docs/getting-starte

    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

  21. 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:

    tekton.dev/docs/getting-starte

    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

  22. 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:

    tekton.dev/docs/getting-starte

    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

  23. 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:

    tekton.dev/docs/getting-starte

    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?

  24. Actually on the topic of feature flags, I'm curious if they exist/what people are doing at the infra / #IaC / #GitOps level.

    At one point I was thinking "can I hookup like launchdarkly into #Puppet's Hiera" to handle phased rollouts of things.

    More recently, want the same thing for my #FluxCD stuff. Higher level than like Flagger I think, as in gradual rollout of Deployments over many clusters, than gradual rollout of Pod within a deployment.

    Kinda like #Ansible's strategies and it's "max_fail_percentage" where it'll halt.

  25. @mattiasb @thibaultamartin oh yes. There are some solutions in between e.g. pi with k3s (my Favorit with #fluxcd)

  26. @hmiron Very similar to mine! I really like #fluxcd but you probably can't go wrong with argo if you choose that path

  27. Okay, authentik is up! Took a while, I was fighting against flux and the helm release because it deployed with the wrong StorageClass (I forgot to have that configuration ready before release.) Helm wasn't able to modify the PVC because they're immutable, updating the release has to wait for the initial release to succeed (which it won't) or timeout and flux is quiet on the reasons for all of this unless you know where to look 😔 lots of learning was had though!

    Anyway, admin and personal user accounts created, MFA enabled. Got my first application integrated too! (actual budget)

    What next? The world is my oyster... Probably gitea or semaphore. I'm hesitant to integrate services like jellyfin before I have more users onboarded and this gives me an opportunity to experiment with other edge cases like other providers and service accounts and such

    #selfhosted #homelab #authentik #sso #fluxcd #gitops #helm

  28. Part of my project for adopting gitops in my homelab has been setting up git hosting. I've selected Gitea for this instead of Gogs because I thought I'd have an easier time bootstrapping fluxcd...

    Now that I've had more time to sit with the docs and learn more about Gitea, I've noticed they have broad support to serve as package registries too! It seems like I can host helm charts and docker images alongside my infra as code! This is fantastic, it'll greatly simplify my architecture. Two birds, one container!

    #gitops #homelab #selfhost #selfhosting #git #gitea #fluxcd #helm #docker #containers

  29. First time immediately jumping to #fluxcd installing a bunch of resources and charts without doing it manually first to get a good understanding of the process. Worked out amazingly well, really no need to even fiddle with manual chart installs and such anymore which is neat. #kubernetes #gitops

  30. Anyone using terraform/opentofu for their homelab setups? Either on infra level or for CM?

    I've made it a project for this year to get everything managed via gitops. I'm taking it step by step and as such I haven't locked down manual write access so that I can tinker with stuff and troubleshoot as needed.

    I'm finding that I need a good way to spot state drift so that I get notified if I forget to correct things afterwards. I think this is going to be less frustrating than fighting against enforced state while I get my bearings.

    I guess I could use a cron or a timer unit. Unless someone has any recommendations? I would like to manage all the TF using fluxcd eventually but I think it's too early to start enforcing desired state right now. I'm open to suggestions...?

    #terraform #opentofu #homelab #selfhost #gitops #fluxcd #IaC #infrastructureascode

  31. 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

    dustinrue.com/2025/03/flux-mon

    #colima #fluxcd #helm #k9s #Kubernetes

  32. 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

  33. What I did in the last weeks (part 2):

    All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.

    In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.

    And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!

    #k3s #homelab #kubernetes #k8s #fluxCD #ArgoCD #GitOps

  34. I maintain the #fluxcd is the better solution (over #argocd) if you are heavily invested in helm. I prefer how it works with helm resources and I prefer that I can still manually take over a helm based resource extremely easily if I need to.

  35. 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!

  36. Азбука: FluxCD — перенастраиваем kubernetes с одного репозитория на другой

    Очень удобным способом настройки кластеров kubernetes является использование GitOps подхода. Его суть заключается в том, что выделяется отдельный git репозиторий, который становится хранилищем всех манифестов, определяющих состояние кластера. Таким образом мы получаем единое хранилище истины и единую точку конфигурации для управления кластером. Одним из пионеров и проповедников этого подхода являлась компания WeaveWorks , в рамках которой было разработано множество интересных решений, среди которых есть и GitOps-оператор FluxCD . Именно он и реализует цикл синхронизации манифестов из git репозитория с кластером.

    habr.com/ru/companies/aenix/ar

    #kubernetes #gitops #fluxcd #gitlab #восстановление

  37. 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 😅

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

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

    link.davinkevin.fr/flux-and-he

    #FluxCD #Kustomize #Helm #DevOps @kubernetesio