I'm trying to set up my existing Cloud function that I've deployed previously with python38. I've deployed without VPC previously and I was able to deploy with no problem. But when trying to set up VPC connector on deployment, I get the following error
(gcloud.functions.deploy) OperationError: code=3, message=Function failed on loading user code. Error message: OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k
I tried to use the GCP UI to create VPC and hook up to the function Egress settings, but I get same error when deploying the changes. Would you know how to overcome this?
Thanks for sharing that info Alvaro, that would be helpful.
Would you know if is there any way to find out whether my requests to these functions will now default to IPv4 instead of IPv6?
In the documentation it says "VPC networks only support IPv4 unicast traffic", does it mean it's always going to be IPV4 unless I switch to a global Load Balancer? cloud.google.com/vpc/docs/vpc#spec...
Hi Alvaro, Thanks for writing this post!
I'm trying to set up my existing Cloud function that I've deployed previously with python38. I've deployed without VPC previously and I was able to deploy with no problem. But when trying to set up VPC connector on deployment, I get the following error
(gcloud.functions.deploy) OperationError: code=3, message=Function failed on loading user code. Error message: OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k
I tried to use the GCP UI to create VPC and hook up to the function Egress settings, but I get same error when deploying the changes. Would you know how to overcome this?
Turns out it's an issue with Python38. I used Python37 and didn't run into this issue anymore.
Hi Alex! good to know that you resolved the issue.
Yep, python 3.8 is in beta on Google Cloud Functions, here is the documentation for the supported Runtimes cloud.google.com/functions/docs/co...
Thanks for sharing that info Alvaro, that would be helpful.
Would you know if is there any way to find out whether my requests to these functions will now default to IPv4 instead of IPv6?
In the documentation it says "VPC networks only support IPv4 unicast traffic", does it mean it's always going to be IPV4 unless I switch to a global Load Balancer?
cloud.google.com/vpc/docs/vpc#spec...
Hi Alex, sorry for the late response, I've been busy these days.
Let me see if I understood your question, do you want to know if you can request a functions via IPv6?
In the post we set a IP for egress traffic, for ingress traffic we still use the URL.
The Load Balancer is a layer that you can use to centralize you different resource in a unique IP address (IPv4 or IPv6).
The HTTP(S) Load Balancer supports Serverless compute (aka Cloud Functions).
Check this post if you are interested on that:
cloud.google.com/blog/products/net...