Local timeline

Replying to a post that is no longer available

@0xWDG what is your use case for this feature?

Replying to a post that is no longer available
Replying to a post that is no longer available

@mookie do you like it? I often wonder about the data accuracy of the sensor.

Replying to a post that is no longer available

@mookie are you already planning your return to GotoSocial, now that @ivory is imminent? :-D

Photo of a 3D printed Christmas cabin
Photo of a 3D printed Christmas cabin

Finished 3D-printing a Christmas cabin. Really liking the outcome. The software allowed for easy changing of the included signs. #3DPrinting #BambuLabs

Finished my first 10K race in 58 minutes and 24 seconds. I'm pretty darn proud of myself.

#running

Replying to a post that is no longer available

@stfn @ben @solarisfire

I do need to add that NFS is somewhat of an anti-pattern for Kubernetes. It's deemed unstable, and is bound to cause issues at some point. Locally in my homelab setup, I have a Synology CSI deployment that mounts block volumes using iSCSI.

Replying to a post that is no longer available

@stfn @ben @solarisfire

For 1) you'll need https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

For 2) you can use my example. It's for mounting existing NFS shares to new Pods.

Replying to a post that is no longer available

@stfn its Helm templating, so it's not directly mappable to regular Pod YAML. You define the NFS volume in the Pod spec, but the volumeMount in the container :)

Replying to a post that is no longer available

@stfn

Neat :-)

FYI: ingress.class annotation is deprecated. You should use the .spec.ingressClassName field instead.

You can mount NFS volumes directly to Pods. Here's a Helm values snippet that I use for my Plex server hosted on Talos Linux:

extraVolumes:
  - name: media-volume
    nfs:
      server: 192.168.1.5
      path: /volume1/media

extraVolumeMounts:
  - name: media-volume
    mountPath: /volume1/media
Two cats grooming each other
Two cats grooming each other

Today's #Caturday contribution: Two oldies grooming each other. 🐱🐱

#Cats #CatsOfMastodon

Tiny sprint intervals to get ready for my first 10K race tomorrow. Hope to finish it under an hour 🤞#running

Replying to a post that is no longer available

@synq @systeemkabouter @Eelcom

Ik heb nog niets gehoord. Klopt dat?

Replying to a post that is no longer available

@stfn Nice! You're taking huge leaps. Well done.

Replying to a post that is no longer available

Woke up to #Bitcoin being a $100k. Nice :-).

Picture of the assembled marble track.
Picture of the assembled marble track.

The 3D-printed marble track came out great. Perhaps I've been enjoying this a bit more than the kid itself.

#BambuLabs #3DPrinting

Replying to a post that is no longer available

@stfn @KevinGimbel

No, you'll lose the k3s LB. It's not very economical to have one LB per service, as most cloud providers charge you for IPs/LBs. For HTTP(s) traffic you'll want to read up on an Ingress Controller. It's a reverse proxy deployment that looks for "Ingress" resources on your cluster, and it will configure the reverse proxy / vhost so you can expose that service/deployment through the Ingress Controller.

The Ingress Controller will handle TLS. It'll look somewhat like World -> Cloud LB -> (Service ->) Ingress Controller -> Service -> Pods.

https://kubernetes.io/docs/concepts/services-networking/ingress/

Replying to a post that is no longer available
Load older posts