Why is this necessary? With Forseti on-GCE, the db_migrator.py script runs after the cloud_sql_proxy service has started. As it stands with Forseti on-GKE (FKE or FGKE?) The cloudsql-proxy container starts with the forseti-server container.
What we will do is make the db_migrator.py an initContainer in the forseti-server pod that will keep failing and restarting until the cloudsql-proxy pod is up and running. Only when it succeeds will the forseti-server container be allowed to start.
This will support
Why is this necessary? With Forseti on-GCE, the db_migrator.py script runs after the cloud_sql_proxy service has started. As it stands with Forseti on-GKE (FKE or FGKE?) The cloudsql-proxy container starts with the forseti-server container.
What we will do is make the db_migrator.py an initContainer in the forseti-server pod that will keep failing and restarting until the cloudsql-proxy pod is up and running. Only when it succeeds will the forseti-server container be allowed to start.