Cool, there are a couple of other things you have to consider when moving to k8s on self hosted with workflows.
Service account error in chart
The borrowed helm chart for temporal: [Bug] ServiceAccount does not act as it should when adding external account 路 Issue #403 路 temporalio/helm-charts 路 GitHub
Cloud proxy issues, good to know about
Google specific: Using cloud_sql_proxy from google activly both on self host and on resources - #4 by juan
Extra containers(sidecar pattern) issues
Helm chart specific for extra containers, reported on documentaiton in intercom:
Hi! This page, self hosted workflows, is really not working. But i think it is the retool chart itself and the line https://github.com/tryretool/retool-workflows-helm/blob/main/templates/deployment_backend.yaml#L247.
Im trying to add an sql proxy sidecar container, ref https://cloud.google.com/sql/docs/postgres/connect-kubernetes-engine#proxy. But the yaml is broken, im trying to go about and fix it but I struggle just a tad bit since im new to helm syntax. But getting there. But I want to drop this messages just incase you guys can tell me if its working or not.
Just trying to add extraContainers fail misserably
Solution: You have to use yaml multiline functionality to send in the extraContainers for the retool backend. It works without this for the temporal chart config
------------------------------------------------------------
Maybe @Isaac-H can update the self hosted workflow documentation for Google, so that people wont hit these issues 