@kyle-zapic wrote:
We’re experiencing HTTP timeouts with file uploads and the Warp Ingress (or maybe just Warp???). Specifically, the upload works as expected, but the response is never returned. Is anyone else encountering issues? Should I post this question on the more general Warp topic instead?
Simplified description of our architecture: Mobile Devices -> Cloudflare -> Warp Ingress -> ASP.NET Core Web Application -> Backend Service -> Azure Storage. (The Warp Ingress, ASP.NET Core Web Application, and Backend Service are all running in a K8s cluster on Azure.)
Our clients, on mobile devices, upload pictures using a HTML5/JavaScript application. The photos are successfully making it into Azure Storage. Additionally, our application is instrumented with Application Insights. Application Insights is logging a successful response code from our ASP.NET Core controller with a total request time on the order of a couple hundred milliseconds. However, the clients get a Cloudflare-generated HTML page indicating a response timeout after many, many seconds of waiting.
I replaced the Warp Ingress with ingress-nginx and “plain” Cloudflare DNS/CDN. This configuration worked exactly as expected. So, for some reason, it looks like we’re getting response timeouts when using Warp.
Any thoughts are greatly appreciated.
EDIT: I should note, we’ve been successfully running through the whole month of January without the high CPU usage previously encountered. Updating the deployment to the latest image version resolved this issue as promised.