Currently in a GCP Serverless deployments where the GCP provider is used to fulfill deployments, any service that uses a non-http protocol can't be run on Cloud Run (e.g. mailslurper or smtp4dev wanting to expose something using with the smtp protocol).
GCP Cloud Run only supports connecting via http/http2 protocols, so we'd need to send deployments that require something different elsewhere.
Google Compute Engine (GCE: https://cloud.google.com/compute/) can be used to deploy a container and we can configure the firewall rules so that the necessary port(s) are exposed. A Cloud Run function that needs to connect via smtps should then be able to use the GCE instances private IP to connect.
Currently in a GCP Serverless deployments where the GCP provider is used to fulfill deployments, any service that uses a non-http protocol can't be run on Cloud Run (e.g. mailslurper or smtp4dev wanting to expose something using with the smtp protocol).
GCP Cloud Run only supports connecting via http/http2 protocols, so we'd need to send deployments that require something different elsewhere.
Google Compute Engine (GCE: https://cloud.google.com/compute/) can be used to deploy a container and we can configure the firewall rules so that the necessary port(s) are exposed. A Cloud Run function that needs to connect via smtps should then be able to use the GCE instances private IP to connect.