🤬 F*CK YOU Broadcom!

YouTube

Adventures in #selfhosting!
I just finished failing to do a "correct" and "proper" upgrade of cloud-native postgres, #cnpg, from using standard #longhorn volume backups to the barman cloud plugin.

I got the plugin loaded accord to the migration docs, but couldn't get it to write to #s3, nor could the pods become ready. I worked at it for hours, but I saw lots of other people online and recently having the same issues and log messages that I was.

The reason I did this in the first place was that I noticed that I had some duplicate backup jobs causing issues with #fluxcd reconciliation.

In the end, I gave up and went back to the original longhorn backups, which have worked and I've already done disaster recovery with (don't ask), and deleted the duplicates.

Currently I'm waiting for the previous primary/write node to fully restart and clear out the barman side car. Then I'll turn flux back on and hopefully things will be good.

#keyboardvagabond #kubernetes #comingSoonTM

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.

Well... Every time I create a repository on my self-hosted Forgejo I set the object format to sha256, because I thought any modern things should work fine.

It so happens that Flux only talks to repos in sha1 format.  

#HomeLab #Forgejo #TalosLinux #FluxCD

@mattiasb @thibaultamartin oh yes. There are some solutions in between e.g. pi with k3s (my Favorit with #fluxcd)
does #helm, #kustomize, #fluxcd #automatoin all *need* to be complicated, all of the time ?

Thankfully no. helm charts in particular can be localized into code bases as part of a greater infra stack and kept simple, as simple as the 'mail merge' like templating in WordPerfect, many moons ago. If you want to that is and there is no need to make things super complicated and hyper optimized for re-use for everything, all of the time. Not unlike a similar principle in SQL - normalization. You can over optimize a database to have it fully 'normalized' only to find you have doubled or more the time taken to execute some queries.

I like the keep it stupid simple approach #kiss whenever possible. I believe Go is a good illustration of a big project like that, kept simple enough to be approachable yet elegant in its design and still highly flexible. Something for us to aspire to. I have a long way to go to match that, but I can dream.

More progress in setting up #talos and #kubernetes!

Because my provider, Netcup, doesn't have a firewall in front of the #vps, I want to set up a #wireguard server to secure things, but that requires storage. Last time I finally got talos to split the SSD into volumes, one part for ephemeral talos, and the rest for #ceph and #ceph-rook.

But for that to work, I also had to do something with #fluxcd (at least as part of the guide I'm following). I think it's working! There's still more to do as far as cleanup and continuing, but I should be able to get #kustomize working soon!

Then, I'll follow more setup steps so that I can finally do what I could have done with #docker on regular #linux lol.

#overcomplicatingThings #putItOnTheResume

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

Project post originally published on the Flux Blog by Priyanka Ravi and Daniel Holbach This is the first blog post in a series where we want to shine a light on projects in the Flux Ecosystem.

CNCF

Handy, especially when working with #FluxCD and you want to see if the change is syncing across, whilst running it in watch(1):

(defun my/copy-short-commit-hash ()
"Copy the current buffer revision, aka git commit, and trim it."
(interactive)
(magit-copy-buffer-revision)
(thread-first kill-ring
car
(substring 0 8)
kill-new))

#emacs