hmmm, ok, I can't say what's going on, but it's an issue with routing between nginx ingress and the service. If it was hitting the service, even if there was an issue you'd get something like "503 service is unavailable". 404 means microk8s ingress isn't even reaching the service