Are you guys crazy? Please allow me to catch up... I am still in awe of the things that I know... And now THIS? What do you expect me to do - stay in awe and NOT do my work... ?? Damn you for being so awesome
thanks for the new updates and they are very nice..one question on traffic splitting. it looks like with the tag and updates traffic i can control the % of traffic to new instance, but if i also want to target the traffic from specific ip address/headers value that would help to test the functionality as a whole end to end. any advice there? also, we presently use gclb that can also help to split the traffic of cloud run if they are to be set with different neg and service versioning , i was wondering what is the ideal way.
Not yet, but there are rumors that they're working on it. 🤞 One of the hosts in another video ("Cloud Functions vs. Cloud Run ") mentions this in the comments.
Will you guys ever support the option to autoscale across regions? I imagine using autoscaling across regions and cloud spanner you could basically take over the world with minimal dev ops
Check this out: cloud.google.com/load-balancing/docs/https/setting-up-https-serverless Covers not only how to set up an LB with Cloud Run but also the other services like CDN and Armor. 😁
It sounded like Cloud Run's support for Identity Aware Proxy is going to depend on using GCP load balancers, is that right? It would be great to see support without needing the load balancer
@@sterengiannini1694 is there anyway to make managed cloud run *internal* and put a load balancer + IAP in the front? I'm developing an internal web app for my company and right now I've managed to put IAP + load balancer in the front, but people can bypass the IAP via auto-generated url by cloud run. If I don't allow public access to that url, http request goes through IAP but will be rejected by cloud run which doesn't suits my use case (company internal web app). I know that if IAP is enabled for App Engine, request to the original app engine url will be redirected to the auth screen, I wonder if cloud run will support similar behaviour or is there any way to deal with people bypassing IAP + load balancer?
if I deploy cloud run to GKE with `--connectivity=internal` and put load balancer + IAP in the front, guess I would be able to avoid people bypassing IAP?
This service alone can be there reason I chose GCP over other cloud platforms every freaking time
Love it, I think we'll move all of our services to Cloud Run soon:D
Cloud Run is the best GCP service I have used so far. Will be moving more services to it.
Awesome work Cloud Run team. Definitely moving all my http functions to Cloud Run
Cloud Run is so awesome 😭
Are you guys crazy?
Please allow me to catch up... I am still in awe of the things that I know... And now THIS?
What do you expect me to do - stay in awe and NOT do my work... ??
Damn you for being so awesome
At 13:25 you mention the ability to run Cloud Run apps locally. Is that only for development or would that also be suitable for production use?
This is only for local development.
Nice presentation. Great work with Cloud Run!
Great features of Cloud run very well explained.
thanks for the new updates and they are very nice..one question on traffic splitting. it looks like with the tag and updates traffic i can control the % of traffic to new instance, but if i also want to target the traffic from specific ip address/headers value that would help to test the functionality as a whole end to end. any advice there? also, we presently use gclb that can also help to split the traffic of cloud run if they are to be set with different neg and service versioning , i was wondering what is the ideal way.
Wow. Impressive features.
LOVE CLOUD RUN!
Love it !!🤗🤗🤗
Great work
Thank you so much 😀
Still not possible to establish websockets?
Not yet, but there are rumors that they're working on it. 🤞 One of the hosts in another video ("Cloud Functions vs. Cloud Run
") mentions this in the comments.
CloudRun is awesome and my GOTO for everything. Great Video & Speaker
You guys are amazing... wow kudos to cloud run team .. thinking it’s gonna replace GKE soon ...
the BEST keeps getting better. nice! but... will we ever be able to assign from a static ip pool?
Will you guys ever support the option to autoscale across regions?
I imagine using autoscaling across regions and cloud spanner you could basically take over the world with minimal dev ops
Thank you!
Great video, where can I find more documentation for integrating cloud run with the WAF Google Cloud Armor?
Check this out: cloud.google.com/load-balancing/docs/https/setting-up-https-serverless
Covers not only how to set up an LB with Cloud Run but also the other services like CDN and Armor. 😁
Thank you for this Video ! , What about supporting websockets ?
I think you can use firebase realtime database or cloud firestore as an alternative since cloud run does not support websockets
Min instances for cloud run makes it a replacement for cloud functions pretty soon! Also any possibility for firestore triggers?
You can use eventarc events for that :)
This is just awesome!
automatic https and custom domain is best
It sounded like Cloud Run's support for Identity Aware Proxy is going to depend on using GCP load balancers, is that right? It would be great to see support without needing the load balancer
That's correct.
@@sterengiannini1694 So I have to provision a load balanced to get the ability to route to different regions?
@@boot-strapper Yes.
@@sterengiannini1694 is there anyway to make managed cloud run *internal* and put a load balancer + IAP in the front? I'm developing an internal web app for my company and right now I've managed to put IAP + load balancer in the front, but people can bypass the IAP via auto-generated url by cloud run. If I don't allow public access to that url, http request goes through IAP but will be rejected by cloud run which doesn't suits my use case (company internal web app). I know that if IAP is enabled for App Engine, request to the original app engine url will be redirected to the auth screen, I wonder if cloud run will support similar behaviour or is there any way to deal with people bypassing IAP + load balancer?
if I deploy cloud run to GKE with `--connectivity=internal` and put load balancer + IAP in the front, guess I would be able to avoid people bypassing IAP?
Already on :)
3:01 'we cover all continents' AFRICA ??????????
Hello