If I deploy workloads to Cloud Run using the console, Direct Egress works fine. When deployment occurs through Github actions (using the beta client), whilst the service is re-deployed successfully, connectivity through to my VPC is broken.
Redeploying a 'broken' revision using the console without change 'fixes' the connectivity issue.
Upon comparing the revision's YAML, the only difference of note is the omission of serving.knative.dev/route label.
I researched what the label related to, it appears it is an istio config element which can indicate whether the service should be routed.
https://knative.dev/docs/serving/troubleshooting/debugging-application-issues/#check-route-status
I tried setting the label from the Github Action, and it worked.