Playing with #Longhorn for the first time. By default it sets up a storageClass with a reclaim policy set to delete. If I'm snapshotting and backing up volumes regularly, are there any major advantages/disadvantages to creating a duplicate storageClass with the reclaim policy set to retain? It seems I shouldn't bother and should instead rely on the backups.

#NewSpecies
New longhorn beetle from #ecuador just came in:

Nealcidion chloroxanthon

Treatment: https://treatment.plazi.org/id/892487AC-7602-FFE5-4FD1-D88EF1CAFE07
Publication: https://doi.org/10.11646/zootaxa.5604.1.1
#Zootaxa #NealcidionChloroxanthon

#FAIRdata
#science #OA #openaccess #biology #taxonomy #ecology #biodiversity #nature #wildlife #conservation #animals #invertebrates #entomology #insects #coleoptera #beetles #bugs #longhorn

Windows #Longhorn: Warum Microsoft den ersten Nachfolger von Windows XP verwarf
https://www.golem.de/news/windows-longhorn-warum-microsoft-den-ersten-nachfolger-von-windows-xp-verwarf-2503-194763.html

This could have been a blog post. :/

#WindowsLonghorn Explained by a Retired Microsoft Engineer

https://youtu.be/RpRZ8BQiiMo

Behold my tale of woe and do not use downloadURL on #Longhorn backingimages where that URL's image might possibly get updated or get 404'd later unless you want to try your luck at tracking down very specific versions of images that the internet has now mostly not forgotten about while stuff fails to launch .

I've got some in-cluster storage now with 3x 512GB NVMEs, i've just fought a little with #Longhorn to get it installed (due to kube-router hairpin mode) and now i'm thinking, is Longhorn the right choice?

I'm wondering if I should look at #Ceph instead as its a bit more tried and tested, I did use Longhorn a while ago and it ended up nearly killing the consumer SSDs I had at the time.

Today’s episode: 'The Longhorn Sisyphean Struggle'

I’m trying to share a #Longhorn persistent volume across services in different namespaces. So far, it’s causing me more trouble than a Greek mythological torment. (What was the guy’s name again—the one doomed to push a boulder uphill forever? Oh right, Sisyphus.)

If anyone has insights, tips, or just moral support, I’m all ears.

More adventures under #SelfHostingChronicles.

#NewSpecies
New longhorn beetle from #ecuador just snuck in:

Antodice apicalis

Treatment: https://treatment.plazi.org/id/892487AC-7609-FFEF-4FD1-DE5AF06BF837
Publication: https://doi.org/10.11646/zootaxa.5604.1.1
#Zootaxa #AntodiceApicalis

#FAIRdata
#science #OA #openaccess #biology #taxonomy #ecology #biodiversity #nature #wildlife #conservation #animals #invertebrates #entomology #insects #coleoptera #beetles #bugs #longhorn

Someone at SCaLE asked me about running #Rancher on #TalosLinux. Strictly speaking, it should be possible in #Harvester since I remember getting it to run in Eucalyptus. It is possible to do #Longhorn in Talos as well, but I don't know about k3s/RKE2, but it doesn't seem practical (or possible, or in any way supported) to do that over Sidero Metal for Talos or SLEMicro for Rancher.

K3s es una versión ligera y simplificada de Kubernetes, diseñada para ser fácil de instalar y gestionar en entornos de producción pequeños y medianos.

Además del LPP, K3s también admite otros proveedores de PV, como:

Longhorn: Un proveedor de PV que utiliza un sistema de archivos distribuido para almacenar los datos de los volúmenes persistentes.

#K3s #PersistentVolume #Longhorn

https://blog.academiadesarrolloweb.com/2025/03/08/longhorn-almacenamiento-en-bloque-distribuido-nativo-en-k3s-kubernetes/

As a #Longhorn, I don't often compliment the denizens of College Station, but kudos to them for fighting against the encroaching #Amazon delivery drone swarm.

#Wired article: https://www.wired.com/story/texas-amazon-drones-stop-flying

Hook em, horns?

Longhorn cows outside of Austin, Texas #Texas #Austin #Longhorn #Cows #Clouds #Sky #Grass

Ok, #Longhorn might have just saved me here with #k3s and my storage woes. #SMB and #NFS both caused catastrophic problems with corrupted files and databases. Using #unraid as the storage backend for the later 2 but will keep it as a backup destination and network storage for more static datasets.

Thanks to everyone who helped push me in this direction. #homeassistant is officially happy again!

Ok, think I need to do the whole #k3s shared storage thing again. As of last night I have both NFS and SMB going, but neither work for #sqlite DBs of course. I get corruptions on NFS and immediate errors on SMB (can’t get exclusive locks). Thinking of trying #longhorn for the shared storage with off-cluster backup.

My primary use case is apps like #homeassistant though, so I’m not sure if I’m overthinking this. I suppose I could configure HA to use a DB like Maria but I have some apps that don’t support this at all to my knowledge, so I’d need something with proper file locking support.

Has anyone gone down this road? Am
I framing this right - Longhorn for most app storage needs, SMB/NFS for larger storages like photos / media?

Notre série dédiée à #cloudNativePG continue !
Cette fois, Julian présente des solutions de stockage et de performance =>
https://dali.bo/202502_cloudnativepg-3

#PostgreSQL #SGBD
#opensource #logicielsLibres
#cloud #CNPG
CloudNativePG
#longhorn #pgbench