XIO

xWire

Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.

Google Developer forums - Topics tagged cloud-run

Topics tagged cloud-run

Recoverability of historical Firebase Cloud Functions Gen 2 artifacts after Artifact Registry returns MANIFEST_UNKNOWN

Hello Google Cloud Community, I’m investigating whether original runtime artifacts for Firebase Cloud Functions (2nd gen) can be recovered after their container images become unavailable through Artifact Registry. I’d appreciate guidance on supported recovery guarantees and read-only verification methods. What I’ve verified Source archives for seven functions have been recovered and checksum-verified. Original function revisions and three successful Cloud Build records were previously…

Cloud Run CPU allocation quota exhausted despite low request traffic and cpuIdle=true

Hi everyone, I’m experiencing repeated Cloud Run CPU allocation quota exhaustion in a Firebase Cloud Functions 2nd gen project deployed in southamerica-east1. The problem Our regional run.googleapis.com/cpu_allocation quota is 20,000. During application testing, utilization reached approximately 93%, and several unrelated functions failed with: The request failed because the project exceeded its quota limit for run.googleapis.com/cpu_allocation recently. Some requests were also aborted because…

Agentic Metadata Governance: discovering and remediating catalog gaps with Knowledge Catalog & Gemini 3

Enterprise data platforms manage tens of thousands of tables, schemas, and views spanning BigQuery, Spanner, and Cloud Storage. While Knowledge Catalog provides a centralized metadata foundation, enterprise catalogs suffer from continuous metadata decay: severed pipeline lineage, unclassified PII, missing policy tags, blank descriptions, and unmonitored schema mutations. Static rule-based validation scripts fall short because metadata evaluation requires semantic reasoning: understanding…

Cloud Run Ready=true, ingress=all, correct IAM, no load balancer -- native *.run.app URL still returns Google 404, zero request logs

My Cloud Run service “noc-hub-prod-triage” is reported Ready=true by the Admin API (terminalCondition=Ready, RoutesReady=CONDITION_SUCCEEDED, ConfigurationsReady=CONDITION_SUCCEEDED), ingress=INGRESS_TRAFFIC_ALL, and allUsers has roles/run.invoker on the service. Container logs confirm gunicorn started successfully and the TCP startup probe on port 8080 succeeded. Traffic is 100% on the latest ready revision. However, the native *.run.app URL (both the human-readable one and the project-number…

[Showcase] gcr-top — A blazingly fast Rust TUI for managing Google Cloud Run

Hello Cloud Run community, I wanted to share an open-source developer tool built in Rust to streamline day-to-day operations and observability for Google Cloud Run fleets: gcr-top. Managing multiple services across regions often means constant tab switching in the Cloud Console or running multiple slow CLI commands. gcr-top brings an htop/k9s-style experience directly to your terminal. Key features: Multi-region aggregation: Query and observe all services simultaneously using ‘–region -’.…

Cloud Run stops routing requests to a healthy instance after an abruptly rejected WebSocket upgrade

We reproduced unexpected behavior in a small Cloud Run test service: A WebSocket upgrade arrives with a malformed URL. Our Node.js service rejects it using socket.destroy() without sending an HTTP response. Cloud Run reports the failed upgrade as HTTP 500 and subsequently stops routing all new requests, including ordinary API requests, to that instance. The application continues running normally, existing WebSockets remain usable, and the liveness probe stays healthy. The instance appears to…

How I Optimized CI/CD Pipeline Costs Using Cloud Build and Cloud Run

Problem Our team was deploying multiple microservices across development, QA, and production environments. The initial setup used dedicated infrastructure with always-on deployments, resulting in monthly costs exceeding $800 for resources that were idle 70% of the time. We needed a cost-effective solution that maintained deployment flexibility without sacrificing reliability. Approach 1. Migrated low-traffic services to Cloud Run Analyzed service metrics and identified APIs with less than 100…

Docker Hardened Image fails to load on Cloud Run

Hello everyone, I’ve been testing the new hardened Tomcat images from dhi.io/tomcat. They run fine in my local Docker daemon, but the container fails to start when deployed to Google Cloud Run. The only message I see in Log-Explorer: Revision is not ready and cannot serve traffic. Container import failed: “ContainerImageImportFailed” For comparison, the DOI image works without issues in the same setup. The only change I made was in my Maven Jib configuration, switching the base image: <plugin>…

Refused to connect Getting 404 Error after connecting my GitHub Enterprise using 2nd gen--Cloud Build How to fix this issue

When I tried to connect to Enterprise GitHub repository to Cloud Build using 2nd gen , the Connection flow is working fine till authentication but once i click on add app it is adding the app and it is redirecting to 404 page in GitHub how to fix it Checked in the GitHub it did added the app. but in cloud build it is enable to connect Steps to reproduce: cloud build→Repositories→2nd gen→ Create Host Connection →GitHub Enterprise This we are it is navigating Fyi I removed my org details in the…

Cloud Run vs Cloud Run Functions

I’m building an API and I need help understanding whether I need Cloud Run, or Cloud Run Functions. I guess they’re not the same service…? Right now, I created a Node.js project, and ran: gcloud run deploy my-function \ --source . \ --allow-unauthenticated \ --region us-central1 But I’m not sure what it creates… a Cloud Run function, or a Cloud Run Function function (?). I’m really confused, so I’d appreciate any help! 4 posts - 4 participants Read full topic