akri VS external-dns

akri: AdmissionErrors and if it actually mounts something the process cant access the device for some reason.

If you're talking about hardware attached to nodes, Akri might be of interest: https://github.com/project-akri/akri

Fun hands on use-case/story. Trying to connect sensors & actuators sounds fun! It's clear that they need some kind of infra/platform that they can run on-prem, & this feels like a lock.

There's a new Dynamic Resource api in k8s 1.26 that feels potentially well suited to managing their various kinds of node-attached resources in a pretty broad/generic/cloudy way. Taking the cloud from anonymous compute/storage nodes to an all encompassing management system for whatever we have is an interesting next step. I rather doubt we'll see folks like this spend the 3x effort to pioneer use of these abstractions but over time it should start to emerge & become more regular. https://kubernetes.io/docs/concepts/scheduling-eviction/dyna...

There's also a really neat really nice CNCF Sandbox project Akri which performs semi-similar-ish functions as Dynamic Resources. One of the examples they use as a goto is managing a fleet of OVNIF cameras, like, security cameras. https://github.com/project-akri/akri

On another topic, appreciate this article talking about the mixed human/robot workflows. Good to consider! I worked at a great & interesting data-warehouse company a long time ago that had some very complex long running ETL pipelines & limited compute resources (good number of boxes... pre-cloud era!), and a lot of time-sensitivity. The company used Jira to manage the ETL end to end, with custom workflows where work would gate, process, get checked through various stages, with processors updating the ticket as work advanced or to report % complete. Intensely sharp choice not to build it ourselves, to use a tool for tracking work, even though the code (robots) we built were doing 9/10ths the work. Fun to see a similar topic discussed here.

Good problem setup, interesting view here. Would appreciate a little more technical specifics, but still fun to see.

You need something to act as the runner queue to schedule the nodes, so perhaps you could pull them into a k8s cluster and auto-scale oh the load queue. Using something like this to tag the nodes what special devices might be attached on certain nodes https://github.com/deislabs/akri

Some notes on Plex/Emby/Kodi and transcoding. If you want true transcoding with GPU acceleration, you have to have Nvidia GPU or be a k8s device plugin genius. The whole idea of mounting elastic devices in k8s is fairly new and rather complex. In the mean time transcoding is best done on a beefy device with a proper CPU (eg i7) or specifically Nvidia GPU because there are numerous pre-made plugins. I just run Plex and Emby on an old ATX gaming machine without GPU acceleration and it works totally fine. They were barely usable for just me when running on the RPis, wouldn't recommend it unless you can figure out how to mount the correct devices in the pod using a custom raspberry pi device plugin . . . lol good luck! - Arm labs device manager: https://community.arm.com/developer/research/b/articles/posts/a-smarter-device-manager-for-kubernetes-on-the-edge - Deis labs Akri device manager: https://github.com/deislabs/akri - Nvidia GPU plugin: https://github.com/NVIDIA/k8s-device-plugin

The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.

One of the reasons why I chose Hetzner was that it WAS supported by the ExternalDNS project. I didn't quite understand why the Hetzner provider was pulled, but I saw that an attempt of re-adding it was refused, on the ground that the upcoming webhook architecture would have allowed to better maintain providers.

Write a custom controller for the external DNS controller, or setup some form of ArgoCD app / appset templating.

so I am looking at having an automated way for new routers registered in Traefik to also have the corresponding DNS entry added to my Pihole instance similar to external-dns but obviously, this is exclusive to ingress on k8s environments. my current setup is traefik in a container on unraid.

You technically don’t need to run a load balancer or have a virtual IP for your control plane. If you control your dns, you can add an A record pointing to all IPs for your control plane nodes. It won’t load balance your traffic, but combined with something like External DNS it gives you HA for the control plane.

I normally deploy external-dns, which automatically updates DNS with the ingress controller's external IP address.

Background: Having a look I can see this https://github.com/kubernetes-sigs/external-dns

3) Use the Kubernetes External-DNS. I've never used this, but this is assuming it can update DNS for each pods/app to point to the correct Node (it'd need to update my Homelab DNS running on Windows Server)

So here’s the solution I have taken for our current stack. EKS and its dependencies are created through terraform using the eks module as well as provision a route53 subdomain and a wildcard cert. Once we have that created, I have installed this deployment into the cluster via the helm module: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/. This allows me to use kuberentes resources (load balancers or ingress objects) and it will handle all the provisioning of load balancers and security groups for me, based on my application yaml and annotations. We also use https://github.com/kubernetes-sigs/external-dns to manage all of our specific host names for the applications through annotations. So to generally put, terraform manages out Kubernetes clusters, and Kubernetes manages the deployment of anything needed for the application including volumes, load balancers, hostnames though Kubernetes system deployments

Metallb for your load balancer (layer2 mode will do) NginX-ingress, will be spot on for internal home apps External-dns to publish your dns record to your Dns server at home, https://github.com/kubernetes-sigs/external-dns