I had Hitachi Enterprise SATA drives for a while and they are bulletproof proof. I cheaped out when I upgrade my capacity by using desktop SATA drives, now I get errors when I push them, apparently they can’t keep up. Serverpartdeals.com has recertified HDD. I haven’t tried them yet because there was a funny clause in the warranty related to Canada…

@John Lohman Yep, those are the ones I had. They may or may not have had a NetApp part number. ;-)

https://all3dp.com/4/bambu-labs-controversial-authorization-control-hits-budget-3d-printers/

@John Lohman excellent. Glad I was able to help, even a little bit.

If you set a root password, you won’t be able to log into the vm remotely. Not 100% sure you can log into the console with the root user in Ubuntu either. A user account needs to be setup, perhaps the install script you used has that user name information within it? What script did you use?

I got this setup on Docker Swarm, using the documentation at: https://jokob-sk.github.io/NetAlertX/DOCKER_SWARM/ One thing I can't figure out, is why the IP being assigned in the the docker-compose isn't being honored. Docker is assigning the first IP address in the range, in my case, I didn't give the config a range, so it is defaulting to the subnet and assigning the first available address of 192.168.1.2, with 192.168.1.1 being the gateway specified. Not ideal of course. I recreated the configs with a unique /30 range on each swarm node, and I get assigned an IP from there. I can live with this, but how can I get this info into my Unbound DNS server when and if the container moves between nodes?

sometimes all it takes is a fresh set of eyes.

@Savor Fit As I recall, kubernetes does not have a built-in storage provider for persistent volumes. If you want to use NFS to provision volumes you can try: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner Or for block storage: https://longhorn.io/ I've set up both in the past, but I do not have any notes detailing what I did. Other than a helm install command for the NFS provider. And a note to myself to use the example in the documentation for testing. LOL. Sorry, I don't recall the specifics for either at the moment. helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \ --set nfs.server=<FQDN of NFS server> \ --set nfs.path=<path on NFS server where volumes will be provisioned> Anyone else have any opinions better than mine?