I've just published a #Vaultwarden #Helm chart on my chart repo

For those who'd like to self-host #Bitwarden on your #Kubernetes cluster, feel free to give this a whirl - Vaultwarden is a fork of Bitwarden that was rewritten from scratch in #Rust.

The reason why I chose to write a chart for Vaultwarden instead of Bitwarden is because from my exploration, it seems the former is simply more suited for self-hosting in your #homelab. It's also supposedly more performant and efficient in terms of resource usage.

https://github.com/irfanhakim-as/charts/tree/master/mika/vaultwarden

This is pretty cool!

#Helm command generator | #Kasten K10 https://install.kasten.io/

Lutèce’s Legendary Pastry Program Has a New Chef at Its Helm https://www.diningandcooking.com/2035210/luteces-legendary-pastry-program-has-a-new-chef-at-its-helm/ #a #at #ce #chef #dc #desserts #eater #francais #france #French #FrenchDesserts #FrontPage #has #helm #its #legendary #lut #new #Pastry #Program) #s

Und weiter geht's mit einem Blog zu #OpenCloud per #Helm in #kubernetes: https://loku.be/250411-opencloud-on-kubernetes-locally-part-1 - das erste kurze Fazit ist "Erste Tests machen Spaß, die UI ist unglaublich snappy." - das ist, worum es uns (auch) geht: Nur wenn die Software bei der Anwendung auch Spaß macht, werden wir als Alternative zu #Bigtech erfolgreich sein.

Helm charts are great for managing applications but a massive pain to prep for initial deployment, am I doing this wrong?

With a new chart, I spend time reading through chart values and reading over the templates to see if certain features are supported by the chart or not. Reading go templates isn't exactly how I enjoy spending my time

When you create a chart, the default template supports a lot of standard features (overriding labels, setting TLS details for the ingress, securityContext, etc) which is fantastic... When I find a ready made chart on GitHub, I find that people have renamed some of these or stripped them out. I'm using NFS storage which means I think about process UID/GID a lot and typically create PVCs manually to be mounted in specific places which sometimes works great and sometimes not so much

I feel like I missed the boat with k8s-at-home which had an incredible collection of ready-made charts but it's a shame it's gone dark since

Gesamtzahlen Verkehrstote 2022
Im Jahr 2022 starben 1.192 Pkw-Insassen (43 % aller 2.788 Verkehrstoten)

Studien zeigen:

- 85–89 % aller Verkehrstoten hatten Kopfverletzungen als Hauptverletzung

- Autofahrer sind überproportional betroffen: Auf jeden getöteten Radfahrer kommen 4,5 Autofahrer mit tödlichen Kopfverletzungen

IMHO sollten Autofahrende dringend nur noch mit #Helm fahren dürfen.

#ÖAMTC zu #OGH-Urteil: Entscheidung mit Signalwirkung für #eBike-Fahrer:innen

Der Oberste Gerichtshof (OGH) hat diese Woche eine sehr weitreichende Entscheidung veröffentlicht: E-Bike-Fahrer:innen, die bei einem fremdverschuldeten Unfall eine #Kopfverletzung erleiden und keinen #Helm getragen haben, müssen sich diesen Umstand als Mitverschulden anrechnen lassen. Die Folge: Auch wenn man nicht am Unfallhergang schuld ist, bekommt man nur einen Teil des sonst zur Gänze zustehenden #Schmerzensgelde's vom Unfallgegner bzw. dessen #Haftpflichtversicherung.

Keine Helmpflicht, aber weitreichende Konsequenzen bei Nicht-Tragen möglich:

Das Tragen eines Helmes ist für E-Bike-Nutzer:innen zwar nicht gesetzlich vorgeschrieben, aber in vergleichbaren Fällen muss man mit ähnlichen Konsequenzen rechnen. Der ÖAMTC rät daher eindringlich, bei Ausfahrten mit einem E-Bike immer Helm zu tragen. Und auch bei #Elektroscootern könnte in absehbarer Zeit eine ähnliche Entscheidung getroffen werden.

https://oekonews.at/oeamtc-zu-ogh-urteil-entscheidung-mit-signalwirkung-fuer-e-bike-fahrer-innen+2400+1226338

#ServiceTröt
@fedibikes
@fedibikes_de
#Autokorrektur
#Fahrrad

Zo zie je maar weer dat niet alleen #fietsers maar ook #OVpassagiers n #helm zouden moeten dragen

#EBike-Fahrer müssen #Helm tragen – sonst tragen sie #Mitschuld an ihren Verletzungen - Recht - derStandard.de › Wissen und Gesellschaft
https://www.derstandard.de/story/3000000266109/e-bike-fahrer-muessen-helm-tragen-sonst-tragen-sie-mitschuld-an-ihren-verletzungen

Ein gepflegtes geht raus an den #GeneralAnzeigerBonn ... #VictimBlaming #Helm

Check out this new lab from @sagikazarmark.com on how to test and release #helm charts with #dagger.
https://labs.iximiuz.com/tutorials/testing-and-releasing-helm-charts-with-dagger-4dcb152e
Mark is a Dagger, Helm, and Go expert. I always learn something useful when looking at his code. Thanks so much for putting this together!

It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!

I can do this stuff!

Next step is getting it to work with an ArgoCD CI/CD pipeline.

<rant>
OK, so however thought up the structure of the #Gitlab helm chart was ... creative, to put it politely.

The chart itself has dependencies, as is common with helm charts.
But it also has a charts directory, which contains 5 other charts. Including one called gitlab.
Which again has a charts directory as well as dependencies.

So, depending on which chart you want to configure, it might be chart-name.something or gitlab.chart-name.something. Oh, they also use global.something or global.chart-name.something.

And as this is not creative enough, some charts are installed if chart-name.install is true. For some it is chart-name.enabled...

But help is near, there is an operator, that does the heavy lifting for you. Oh wait, it uses the values from the helm chart of its CRD...
</rant>

Show HN: Koreo – The platform engineering toolkit for Kubernetes
https://koreo.dev/
#ycombinator #YAML #Infrastructure_as_Code #IaC #Platform_Engineering #DevOps #Kubernetes #Configuration_Management #Resource_Orchestration #Helm #Kustomize #Koreo

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