troet.cafe ist Teil eines dezentralisierten sozialen Netzwerks, angetrieben von Mastodon.
Hallo im troet.cafe! Dies ist die derzeit größte deutschsprachige Mastodon Instanz zum tröten, neue Leute kennenlernen, sich auszutauschen und Spaß zu haben.

Verwaltet von:

Serverstatistik:

7,2 Tsd.
aktive Profile

Mehr erfahren

#puppet

6 Beiträge6 Beteiligte2 Beiträge heute
Antwortete defnull

When I say 'drop-in replacement' I mean it: #OpenVox 7.x up to 8.11 is functionally equivalent to #Puppet. The commands and configuration files are the same. You just uninstall puppet-agent, install openvox-agent, and that's it. There is absolutely no reason to pay Perforce (who bought Puppet inc. in 2022) for access to open source software.

Today is the day. #Puppet is dead, long live #OpenVox

Background: Perforce bought Puppet in 2022, betrayed the #FOSS community and changed the license. This resulted in a #fork called #OpenVoxProject, but old puppet releases still worked, so many #DevOps did not care enough to switch.

Yesterday the release key for the free puppet packages expired. It is unlikely that they will renew those keys.

It's time to move on. voxpupuli.org/openvox/ is a drop-in replacement. #FOSS saved the day again!

Vox PupuliOpenVox Automation FrameworkVox Pupuli is a collective of Puppet module, tooling and documentation maintainers working together for the greater good.

Dear #LazyWeb / #lazyfedi,

I'm new to #k8s and am wondering how to handle templating large amounts of config files. I couldn't find anything super useful in my search so I have an #Ansible sidecar I run to generate the kustomizations and config files. My most recent Ansible change was 30 lines, it resulted in changing 5,000 lines of YAML which will further be fed to Kustomize.

There has to be a better way?

I've heard about Helm, Yoke, KRO, and using an operator pattern. My understanding of those options is:

* Helm - My Org recommends avoiding (I don't know why)
* KRO - Not stable, but FFS neither is Kustomize
* Yoke - Almost kinda operator pattern
* Operator Pattern - This feels like reinventing a fucking config manager (ala #Ansible, #Puppet, #Chef, #Saltstack) for every fucking project. What new hell this is.

I'm hoping I'm missing something because the only workable flow for this workload is:
1) Create ansible roles/playbook to generate the kustomization.yaml and resources
2) Generate those kustomizations, check them into git
3) Use Kustomize via GitOps to expand the YAML even more
4) Push a metric fuckton of YAML to production

I'm losing my mind over here.

Alles über #OpenVox auf der SLAC 2025: #Puppet Open Source wird nicht mehr weiter entwickelt. Stattdessen gibt es mit "Puppet Open Core" ein Produkt, das nicht mehr Open Source ist. Die Open-Source-Community hat reagiert und ein neues Projekt Namens "OpenVox“ erstellt.

Martin Alfke von betadots ist erfahrener Puppet-Profi und hält auf der Secure Linux Administration Conference 2025 einen Vortrag zum neuen OpenVox.

Jetzt anmelden – wir sehen uns vom 2.-4.6.25 in Berlin!
slac-2025.de