techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.4K
active users

#puppet

14 posts8 participants0 posts today

The thing is, the Ukrainian people have seen him step up and do everything possible to protect and help them. They also know the type of bit*hes putin and trump are, unlike 1/3 of america they won't vote against their own best interest. And unlike 1/3 of america they won't sit out the vote on "moral grounds". I imagine it's a lot easier to place a puppet when they don't see a real leader in front of them.
#putin #trump #puppet #politics #Ukraine #Zelensky

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.