nut VS ingress-nginx

> what software do you recommend for gnu/linux to take input from the UPS to tell the laptop to shutdown?

https://networkupstools.org/

The Synology software is based on N.U.T. https://networkupstools.org and the Plus 1100 (listed on NUT as the Easy Power 1200) is supported in the native package with the 'blazer' driver. If you have the skills, I would SSH into the NAS and see if the device is 'noticed' or better yet recognised by the USB sub-system when you plug it it. (Normal Linux would use the lsusb command to see devices but I have no NAS handy to see if this is valid on the Synology)

Others have answered the hardware part of your question. I have not seen much mention about the software to control graceful shutdowns. For this I suggest you look at the ”Network UPS Tool” (NUT for short) project (https://networkupstools.org/). It is mostly manufacturer agnostic with clients for a vast array of hardware components.

You're looking for NUT.

Network UPS Tools is one option: https://networkupstools.org/

APC is giving me pre-nut clarity.

So no, the NAS does not monitor the battery level. The UPS does that. The NAS just acts on the messages it receives from the UPS via Synology's version of NUT - Network UPS Tools (https://networkupstools.org/). The NAS will first receive the ON_BATTERY/POWERFAIL signal. Then, eventually the BATTERY_LOW signal at which time the UPS will shutdown. So you really need to set a time for it to shut down *BEFORE* you get BATTERY_LOW.

# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )

ingress-nginx

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.

resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml

For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.

The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace

helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list

Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.