Not really, in my case it's just that I either access it from home or through VPN, so I don't need to expose it outside of my home and work networks.
lidstah
Everything runs in a kubernetes cluster hosted on my homelab, except the public services access point which is a VM hosted on a non-profit ISP and service provider infrastructure, which I contribute to, through a wireguard VPN between the VM and home:
Public-facing:
- an old static website (nginx-unprivileged), which was my first website and which I keep online because nostalgia
- Ghost, personal blog
- OpenSMTPd + rspamd + dovecot (dovecot only accessible from home, not public)
- privatebin
- picoshare
- Whoogle + Tor
- SearxNG
Work related (I work from home 75% of time), not public-facing:
- dolibarr ERP for managing prospects and clients billing
- gitea
- bookstack for personal documentation
- edit: forgot Harbor as container registry.
- vaultwarden
- eck-operator
- wireguard operator for personal, family and friends access from outside
- awx operator
- draw.io
- zalando postgresql operator for postgres needs
- mariadb-galera for mariadb needs
- bitlbee-libpurple for all clients' slack needs
- Authentik as OIDC/LDAP/SAML provider (also used to identify family and friends)
- internal DNS (pdns-resolver + powerdns with postgres backend) serving work zone and home zone.
Home stuff, not public-facing:
- Games: Minetest, EQEmu server (Everquest), planar ally, bzflag, veloren
- Home-cinema/music: Jellyfin, Koel, alltube, and the usual tools to share Linux isos.
- Immich to sync photos
- homeassistant (more a PoC than anything else right now)
- mealie for recipes (I like cooking original meals for friends and family) and lunch/dinner planning
- another instance of vaultwarden for family
- piHole to keep the children a bit safer online (notably blocking malware/scams/nsfw sites)
all of this running on a 3 control-planes/6 workers talos linux k8s cluster, itself hosted on a franken-proxmox cluster (a mix of server/"old" desktops/Ryzen NUCs) and a bunch of NAS (VM dedicated NAS, data storage NAS, backup NAS).
I had the same problem with the kubernetes lemmy.ml community yesterday night, but this morning I was able to find it through the search and subscribe to it (although for the moment it seems quite calm to say the least :)). I'm probably wrong here, but the lemmy.ml staff posted an announcement stating it was quite overloaded with the influx of new users - maybe to keep things afloat they are rate-limiting some resource-hungry api calls?
edit: also, as @anthonyg just mentioned, it might also be a propagation time between instances - if I understand correctly the sdf lemmy instance is quite recent.
- almost everywhere: HAProxy. I like the syntax, ACLs, map files, stick-tables... there's too much to say in a single post, but I use it since 2012 and it never failed me, whatever the need, both at home and at work.
- kubernetes: ingress-nginx. Mostly because it's the first one I tried back in the days and it just works :). Although I should try one of the haproxy based ingresses, or Traefik, which seems interesting too.
Back in the days, I used the SDF free unix shell, which helped me alot to learn more about UNIX basics, and motivated me to iterate my first franken-homelab with bits of old laptops and desktops. If I'm an happy sysadmin nowadays, it's part thanks to SDF.
Then with a bunch of good friends we started our non-profit ISP (circa 2010) and diversified the services we offer to our users (VPS, VPNs, shells, Wiki, BBB, "cloud" (ahem) storage, monthly tutorials and workshops...). Nowadays we have half a rack of servers, and, home-side, my homelab grew (although it's still a franken-lab with NUCs, old desktops and one "real" server). Once again, thanks to SDF for igniting the spark which gave us the will to start our own community of kind and pasionnate people.
With the current reddit debacle, although I don't use SDF services nowadays, I was happy to see that SDF hosts a lemmy instance, because I know the values of the SDF community. So, thank you - again - SDF!
Physical machines get stars names: Vega, Arcturus, Polaris, Fomalhaut, Deneb, Antares, Procyon, Algol, Aldebaran... and so on.
Virtual machines naming scheme is more reasonable: [os]-[role][number if needed]. Examples: