-
🚀 Today at #GoogleNext19, we are launching Cloud Run. Allowing you to run any stateless http container in a fully managed environment, paying only for the exact resources you use. 📦☁️ 👉 cloud.google.com/run
-
…in reply to @steren
😕 Developers love serverless, but feel limited by the available programming languages or the need to rewrite using functions. 👉 Cloud Run brings the properties of serverless to containers: no infra management, fast autoscaling and pay per use.
-
…in reply to @steren
Sometimes, you want more control or have to run on top of Kubernetes, we are also introducing Cloud Run on GKE. Allowing you to run the same serverless workloads with the same developer experience, in your own GKE cluster. cloud.google.com/run/docs/quickstarts/prebuilt-deploy-gke
-
…in reply to @steren
🙏 to the thousands alpha and beta testers who have been using Cloud Run in the past months, providing feedback and reporting issues. You helped us shape Cloud Run!
-
…in reply to @steren
Cloud Run and Cloud Run on GKE both implement the KnativeProject API. An OSS project we introduced last year. This allows you to deploy the same autoscaled services to a fully managed GCP environment, to your own GKE cluster, or anywhere #Kubernetes runs with #Knative.
-
…in reply to @steren
😎I started a collection of awesome Cloud Run related things (articles, docs, containers, tools): github.com/steren/awesome-cloudrun Feel free to send suggestions via Pull Requests.
-
…in reply to @steren
🎬 How to build with Cloud Build and deploy to Cloud Run by BretMcG and martinomander: youtu.be/nJ0L28ZfmUA
-
…in reply to @steren
🌍 Cloud Run integrates with Firebase Hosting. This allows you to create webapps with dynamic endpoints using Cloud Run. All of this behind a global CDN out of the box: firebase.google.com/docs/hosting/cloud-run
-
…in reply to @steren
Firebase Very excited to partner with stackblitz for this amazing in browser developer experience: 1. Start by picking your stack 2. Get a GitHub repo and the prod app on Cloud Run 3. Iterate on the code using an in-browser VS Code-like editor Read more at medium.com/stackblitz-blog/google-cloud-meet-stackblitz-da13f4e4fc29?1
-
…in reply to @steren
Firebase stackblitz And we are very proud to count datadog as a launch partner, allowing you to monitor your Cloud Run and Cloud Run on GKE services: datadoghq.com/blog/monitor-google-cloud-run-with-datadog/
-
…in reply to @steren
Firebase stackblitz datadog If you encounter issues or have questions about Cloud Run, please post on StackOverflow with the tag
google-cloud-run
. Many googlers and myself are monitoring this tag and will be happy to help you stackoverflow.com/questions/tagged/google-cloud-run -
…in reply to @steren
Firebase stackblitz datadog StackOverflow As the name implies, Cloud Run pairs great with Cloud Build. Did you know that you can set up Continuous Deployment of your git repository to Cloud Run using Cloud Build? Docs at 👉 cloud.google.com/run/docs/continuous-deployment
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow Cloud Run now has direct support for Cloud SQL (in alpha). When enabled, we activate and configure the Cloud SQL proxy for you. See temporary instructions here: stackoverflow.com/a/55892255/481649 We are working on publishing docs and moving it to Beta within 10 days. (cc gabidavila)
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila ✨cloud.run now redirects to the Cloud Run product page 😎
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila One month after the launch of Cloud Run, we are pleased to launch several new features to address your top requests: 🧮Cloud SQL support, 📈Metric at a glance, 🌍Europe and 🌏Asia regions opening soon. Read more: cloud.google.com/blog/products/serverless/cloud-run-bringing-serverless-to-containers
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila As promised, Cloud Run (cloud.run) is now available in 🌍Europe and 🌏Asia. You can now picked from these 4 GCP regions: - asia-northeast1 (Tokyo) - europe-west1 (Belgium) - us-central1 (Iowa) - us-east1 (South Carolina)
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila Cloud Run will now only support HTTPS (because it's 2019)
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila 🏷️You can now set labels on your Cloud Run services. cloud.google.com/run/docs/configuring/labels You can then filter billing, logs or metrics. Use cases include cost center / team ownership, environments (env:prod)...
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila 🗄And today, we are announcing Cloud Run for Anthos, allowing you to get the same Cloud Run developer experience and scalability on-premises: cloud.google.com/blog/topics/hybrid-cloud/anthos-simplifies-application-modernization-with-managed-service-mesh-and-serverless-for-your-hybrid-cloud
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila 👩💻The Cloud Run API is now "v1": cloud.google.com/run/docs/reference/rest/ This new API is an implementation of the recently released Knative Serving v1 API. "v1" means that you can expect stability and long term support. One step closer to general availability!
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila 📊 Many of you wanted to better understand how much Cloud Run scales and how many instances are scheduled. We added a new chart to the Metrics tab that should answer this question. E.g. if ou see "2s/s", that means 2 instances were continuously serving traffic in this second.
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila 💥Since Beta, Cloud Run has integrated with Stackdriver Error Reporting out of the box (cloud.google.com/run/docs/error-reporting) We are now surfacing a summary of your top errors right in the Cloud Run user interface:
-
…in reply to @steren
Firebase stackblitz datadog StackOverflow gabidavila ☑️If you have 2 minutes, help us prioritize the next Cloud Run features by taking this short survey: forms.gle/irVTCQ5LTVLPXTqr6
-
…in reply to @steren
🏥 Serverless containers for healthcare: Cloud Run is now covered by GCP HIPAA compliance cloud.google.com/security/compliance/hipaa/#covered-products
-
…in reply to @steren
🎬 I created a Youtube playlist of my recommended Cloud Run related videos: youtube.com/watch?v=gx8VTa1c8DA&list=PLyAgaU37vE7S_Jjt8p6tL1LLmwKziRZjl
-
…in reply to @steren
🏅 Cloud Run is now Generally Available cloud.google.com/blog/products/serverless/knative-based-cloud-run-services-are-ga
-
…in reply to @steren
🤝A broad ecosystem of partners are supporting Cloud Run: CI/CD, Observability and Security cloud.google.com/blog/topics/partners/expanding-the-serverless-ecosystem-for-cloud-run
-
…in reply to @steren
🆕Along with General Availability, came many new cloud.run features. glaforge and I wrote about them in cloud.google.com/blog/products/serverless/a-developers-guide-to-new-features-in-cloud-run
-
…in reply to @steren
glaforge 📜 The Service Level Agreement (SLA) for Cloud Run (fully managed) has been updated to 99.95% cloud.google.com/run/sla
-
…in reply to @steren
glaforge 📄The cloud.run product page has been re-designed and now includes a list of common use cases cloud.google.com/run/#use-cases
- …in reply to @steren
- …in reply to @steren
-
…in reply to @steren
🔵🟢 Cloud Run now has support for rollbacks, gradual rollouts (blue/green deployments), and other traffic migration manipulations between Cloud Run Revisions. Use the Cloud Console or
gcloud run services update-traffic
. More at cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration -
…in reply to @steren
🏗️The cloud.run user interface now displays link to the build information of the deployed container, as well as the repo and commit used to build it (if you are using a Cloud Build Trigger)
-
…in reply to @steren
🖧 Your Cloud Run services can now connect to VPC networks, for example to access Memorystore Redis and Memcached. Use it now: 1. Create a Serverless VPC Access connector: cloud.google.com/vpc/docs/configure-serverless-vpc-access 2.
$ gcloud alpha run services update SERVICE --vpc-connector CONNECTOR
-
…in reply to @steren
🏗️ @GCPcloud has released a set of Buildpacks to help you build containers in Go, Node.js, Python, Java and .Net without having to maintain any Dockerfile. The resulting containers are optimized for production and for the Cloud Run environment. github.com/GoogleCloudPlatform/buildpacks
-
…in reply to @steren
📝Cloud Run is now supported in Cloud Code for both code and intellijidea. 1 Bootstrap with samples 2 Explore your services 3 Deploy - VSCode: marketplace.visualstudio.com/items?itemName=GoogleCloudTools.cloudcode - IntelliJ: plugins.jetbrains.com/plugin/8079-cloud-code
- …in reply to @steren
- …in reply to @steren
- …in reply to @steren
-
…in reply to @steren
You can now use Cloud CDN on top of Cloud Run. By sending the right
Cache-Control
headers, you can drastically reduce the load on your Cloud Run service. Get Cloud CDN via External HTTP(S) Load Balancing: cloud.google.com/load-balancing/docs/negs/serverless-neg-concepts -
…in reply to @steren
🌎🌍🌏Expose a global endpoint that routes requests to the closest Cloud Run service by using a HTTPS Global Load Balancer. cloud.google.com/load-balancing/docs/negs/serverless-neg-concepts
-
…in reply to @steren
📄🚀 Set up Continuous Deployment from git to Cloud Run in just a few click in the Cloud Run UI. This flow is powered by a Cloud Build trigger that automatically builds and deploys when new changes are pushed to your repo. cloud.google.com/run/docs/continuous-deployment-with-cloud-build
-
…in reply to @steren
Cloud Run can now connect to Shared VPCs. Allowing you to connect to private IPs of resources from other GCP projects of the same organization. Read more: cloud.google.com/run/docs/configuring/connecting-vpc#shared-vpc
- …in reply to @steren
-
…in reply to @steren
🔵🟢 You can now reach a specific Cloud Run revision by "tagging" it, it is then available at a dedicate URL https://[tag]---[servie-url].a.run.app This completes the gradual rollout story. Read more on the @GCPcloud blog: cloud.google.com/blog/products/serverless/cloud-run-now-supports-gradual-rollouts-and-rollbacks
-
…in reply to @steren
🔒Data Residency: We made it clearer that when you create a Cloud Run service in a region, your data and container stay in that region. cloud.google.com/terms/data-residency
-
…in reply to @steren
📄📦 When setting up Continuous Deployment from the Cloud Run user interface, you can now select a repository that contains Go, Node.js, Python Java or .NET Core code. It will be built using Google Cloud Buildpacks without needing a Dockerfile (github.com/GoogleCloudPlatform/buildpacks)
- …in reply to @steren
-
…in reply to @steren
⛩️ Introducing Google Cloud API Gateway. A fully managed gateway for your Cloud Run services. See it in action at youtu.be/Hl-wtmfJMOk Read more at cloud.google.com/api-gateway
-
…in reply to @steren
We partnered with pomerium_io, an open source identity-aware proxy, to enable you to build secure internal applications on Cloud Run. cloud.google.com/community/tutorials/cloud-run-with-pomerium-for-end-user-access
-
…in reply to @steren
📝 Cloud Code for VSCode and IntelliJ now has support for running your Cloud Run locally, allowing you to run or debug in an emulated environment. Blog post: cloud.google.com/blog/products/application-development/cloud-run-is-integrated-with-cloud-code
- …in reply to @steren
- …in reply to @steren
- …in reply to @steren
- …in reply to @steren
-
…in reply to @steren
🌐 Static outbound IP: You can now route all outbound requests to your VPC network, allowing you to configure a static outbound IP address via Cloud NAT. Check out ahmetb's tutorial: cloud.google.com/run/docs/configuring/static-outbound-ip
-
…in reply to @steren
❄️🔥 Goodbye cold starts: You can now specify a minimum number of container instances to be kept warm and ready to serve requests. When they are not serving requests, CPU is 10x cheaper than normal. cloud.google.com/run/docs/configuring/min-instance
- …in reply to @steren
- …in reply to @steren
- …in reply to @steren
-
…in reply to @steren
To help us shape the future of Cloud Run, participate in our research studies: g.co/userresearch/xttqs5
- …in reply to @steren
-
…in reply to @steren
🔎 We published a tutorial showing how to use Cloud Run revision URLs to implement previews of GitHub pull requests: cloud.google.com/run/docs/tutorials/configure-deployment-previews
-
…in reply to @steren
📄 To simplify getting started with Cloud Run, we added a single command to build and deploy your source code: $ gcloud beta run deploy --source . - If a Dockerfile is present, it's used - If not, language is automatically detected with GCP Buildpacks cloud.google.com/blog/products/serverless/build-and-deploy-an-app-to-cloud-run-with-a-single-command
- …in reply to @steren
-
…in reply to @steren
📶Cloud Run now allows to restrict ingress of your services to "internal traffic" and "internal traffic and traffic from Cloud Load Balancing". Basically disabling the default endpoint, making the service "private" from a networking perspective. cloud.google.com/run/docs/securing/ingress
-
…in reply to @steren
⚡️ Cloud Run now supports WebSockets, HTTP/2 and bi-directional gRPC streaming! Read more at cloud.google.com/blog/products/serverless/cloud-run-gets-websockets-http-2-and-grpc-bidirectional-streams
- …in reply to @steren
-
…in reply to @steren
🇵🇱 GCP opened a new region in Warsaw, Poland. Cloud Run is available there from day 1. googlecloud/1382372305343549441
-
…in reply to @steren
🔒 Today we are announcing 4 new security features 1. Secret Manager integration 2. Binary Authorization 3. Customer Manages Encryption Keys 4. Security Recommendations I wrote about these at cloud.google.com/blog/products/serverless/improving-the-security-of-your-cloud-run-environment
-
…in reply to @steren
💸 Today, we’re also introducing self-service spend-based committed use discounts for Cloud Run, which let you commit for a year to spending a certain amount on Cloud Run and benefiting from a 17% discount! Read more: cloud.google.com/blog/products/serverless/introducing-committed-use-discounts-for-cloud-run
-
…in reply to @steren
🔒 Cloud Run now supports VPC Service Controls. Allowing you to add Cloud Run services to a VPC-SC perimeter and to restrict Ingress and Egress to / from your service. Why? to manage data exfiltration risks. cloud.google.com/blog/products/serverless/cloud-run-gets-enterprise-grade-network-security-with-vpc-sc
-
…in reply to @steren
🚀 From code to cloud in 3 words: gcloud run deploy
$ gcloud run deploy
now defaults to building source code from the current folder and deploying it to Cloud Run, with support for Go, Node.js, Python, Java and .NET Core, as well as Dockerfile. cloud.google.com/run/docs/deploying-source-code -
…in reply to @steren
🕒 Until now, Cloud Run did not allocate CPU outside of request processing. You can now opt-into having CPU allocated for the entire lifetime of the container instances, price is different: no per-request fee and -25% on CPU / -20% on memory cloud.google.com/blog/products/serverless/cloud-run-gets-always-on-cpu-allocation
- …in reply to @steren
-
…in reply to @steren
Cloud Run is getting a new execution environment (in Preview) with: ✅ Increased network and CPU performance ✅ Full Linux compatibility ✅ Network File System support Docs: cloud.google.com/run/docs/configuring/execution-environments Cloud Storage FUSE tutorial by AveriKitsch: cloud.google.com/run/docs/tutorials/network-filesystems-fuse
- …in reply to @steren
-
…in reply to @steren
💰 Committed use discount recommender now automatically generates recommendations to purchase Cloud Run committed use discounts based on historical usage. cloud.google.com/docs/cuds-recommender cloud.google.com/run/cud These recommendations are notably surfaced in the Cloud Run UI:
-
…in reply to @steren
⚡ Cloud Functions is now powered by Cloud Run. Allowing you to benefit from all Cloud Run features like concurrency, large instances or long processing times while retaining a simple function experience. Give a try to Cloud Functions gen 2: cloud.google.com/blog/products/serverless/introducing-the-next-generation-of-cloud-functions
- …in reply to @steren
- …in reply to @steren
-
…in reply to @steren
✅ You can now define service-level objectives (SLOs) for your Cloud Run services cloud.google.com/stackdriver/docs/solutions/slo-monitoring
-
…in reply to @steren
Why restrict Cloud Run to request-driven services? Today at #GoogleIO, we are introducing Cloud Run jobs to execute code and containers to completion on Cloud Run. Use jobs for batch data transformation, administrative tasks or scheduled jobs. cloud.google.com/run/docs/overview/what-is-cloud-run#jobs
- …in reply to @steren
-
…in reply to @steren
📰 The Cloud Run documentation now captures Terraform instructions alongside Console, Command Line and YAML: cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#terraform Find all samples at github.com/terraform-google-modules/terraform-docs-samples
-
…in reply to @steren
✅ Is the container ready to receive traffic? Cloud Run now allows you to define custom TCP and HTTP startup probes: cloud.google.com/run/docs/configuring/healthchecks
-
…in reply to @steren
🛳️ Cloud Deploy now has direct support for Cloud Run. Manage the release of your container images between dev, staging and production environments: cloud.google.com/deploy/docs/run-targets
-
…in reply to @steren
⚡️ Faster cold starts for Cloud Run: Startup CPU Boost provides additional CPU during container instance startup time. We observed Java Spring Boot apps starting twice as fast with this feature enabled. cloud.google.com/run/docs/configuring/cpu#startup-boost
-
…in reply to @steren
BigQuery and Cloud Run: Did you know that you can implement custom BigQuery remote functions using Cloud Run HTTP services? cloud.google.com/bigquery/docs/reference/standard-sql/remote-functions
-
…in reply to @steren
❌Is the container healthy? If not, restart it. Cloud Run now allows to define custom HTTP liveness probes: cloud.google.com/run/docs/configuring/healthchecks#liveness-probes
-
…in reply to @steren
📊🐶 New official datadoghq instrumentation for Cloud Run just dropped! Collect logs, metrics and traces in real-time via in-container Agent: datadoghq/1578121714017468436?s=03
-
…in reply to @steren
🔒 Don't store API keys or passwords in env vars! 3 new recommendations help you secure your Cloud Run services: Move API keys and passwords to Secret Manager. Use built-in workload identity rather than copying credentials in the container. cloud.google.com/run/docs/recommender
-
…in reply to @steren
🧩 With Cloud Run integrations: - Attach a Redis cache to your Cloud Run service in one click cloud.google.com/run/docs/integrate/redis-memorystore - Replace a dozen of CLI commands to set up a custom domain using an Global External Load Balancer by 1. enter domain, 2. update DNS cloud.google.com/run/docs/integrate/custom-domain-load-balancer
-
…in reply to @steren
🐙 Google is providing official GitHub Actions to deploy to Cloud Run: Check this video by martinomander to learn more youtube.com/watch?v=DMCi7WWTtX0
-
…in reply to @steren
🏗️ Skaffold V2 has built-in support for Cloud Run (Skaffold is a command-line tool that facilitates continuous development and delivery for containerized applications). Blog: cloud.google.com/blog/products/application-development/skaffold-v2-is-generally-available/ Docs: skaffold.dev/docs/pipeline-stages/deployers/cloudrun/
- …in reply to @steren
-
…in reply to @steren
📨 Proxy a private Cloud Run service locally with
gcloud beta run services proxy <SERVICE>
. Making it easier to test a private website or API on your dev machine. No need to inject an auth header via curl anymore. cloud.google.com/run/docs/authenticating/developers -
…in reply to @steren
🐋 Better late than never: you can now deploy to Cloud Run public container images from Docker Hub cloud.google.com/run/docs/deploying#images
-
…in reply to @steren
🔐 Internal and Regional External HTTPS Load Balancer integrations with Cloud Run are now GA cloud.google.com/blog/products/networking/google-cloud-internal-load-balancers-support-cloud-run-services
-
…in reply to @steren
🪪 Identity-aware Proxy (IAP) for Cloud Run is now GA. Create internal web apps with login screen and only grant access to users in your org. cloud.google.com/iap/docs/enabling-cloud-run