Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

344K
active users

mastodon.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-nightly.2025-04-01

#puppet

16 posts10 participants8 posts today
Continued thread
Public *
James Hannah

I found another part of this - after a few weeks, enabling the rotation does seem to have improved the log persistence behaviour on most of our hosts, but I've noticed that a small number (specifically some that lots of users can login to over SSH) were still losing logs, only having one or two archived system journal files.

It turns out that another default for journald is `SystemMaxFiles=100`, and in our configuration - you get one `user-$UID.journal` file for every user that logs into to the box - and therefore on boxes used by >100 people, we were losing the archived files.

Hopefully the #puppet change in just deployed increasing the limit will fix this issue once & for all!

#systemd
Public
MelancholicBear

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.

Public
Brad L. :verified:

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.

ExploreLive feeds
About