One of our staging environments is showing 404 Not Found from NGINX after the deployment.
The deployment does not show an error and the health checks seem to be OK. I have also checked Cloudwatch logs to see if I spot any issues but nothing so far.
Just checked, you cluster was somehow deploying for couple days.
We cancelled and trigger an update on the cluster, issue should be fixed within the next 10 minutes.
We have made a patch for this issue, it will be shipped next Monday on our side, so error shouldn’t happen again.
I keep an eye on your cluster deployment in the meantime.
Unfortunately, it seems update didn;t went through to your cluster because you did the 1.29 upgrade on AWS console directly (not via Qovery). While 1.29 support should be out soon, we cannot properly update your cluster with nginx change as of now, hence your applications facing 404 because wrong ingress classes are set.
You have two options:
1- create a new cluster and migrate your workload on it;
2- wait for us to support 1.29 (couple weeks). In the meantime, you won’t be able to make any changes on your cluster (advanced settings, node types, etc) and we would need to manually patch your cluster to declare the old ingress class.
While the option 1 seems to be the better one, please let me know if you pick the second one.