mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 00:45:19 +00:00
[GCP] Fixed typo in terraform instructions - readme.md (#17025)
This commit is contained in:
parent
ba35b8031d
commit
6d2a57ec83
@ -11,8 +11,7 @@ dns_name = "<the domain you want to host fleet at>" // eg. myfleet.fleetdm.com
|
||||
|
||||
#### Fleet server
|
||||
The fleet webserver is running as [Google Cloud Run](https://cloud.google.com/run) containers, this is very similar to how the existing terraform for AWS runs fleet as Fargate compute.
|
||||
_NOTE: Cloud Run has [limitations](https://cloud.google.com/run/docs/deploying#images) on what container images it will run_. In our deployment we create
|
||||
and Artifact Registry and deploy the public fleet container image into Artifact Registry.
|
||||
_NOTE: Cloud Run has [limitations](https://cloud.google.com/run/docs/deploying#images) on what container images it will run_. In our deployment we create and deploy the public fleet container image into Artifact Registry.
|
||||
|
||||
#### MySQL
|
||||
We are running MySQL using [Google Cloud SQL](https://cloud.google.com/sql/docs/mysql/introduction) only reachable via [CloudSQLProxy](https://cloud.google.com/sql/docs/mysql/connect-admin-proxy) and from Cloud Run
|
||||
@ -51,4 +50,4 @@ Push to Google Artifact registry:
|
||||
|
||||
In this example we are using [GCP Managed Certificates](https://cloud.google.com/load-balancing/docs/ssl-certificates/google-managed-certs) to handle TLS and TLS termination at the LoadBalancer.
|
||||
In order for the certificate to be properly issued, you'll need to update your domain registrar with the nameserver values generated
|
||||
by the new Zone created in GCP DNS.
|
||||
by the new Zone created in GCP DNS.
|
||||
|
Loading…
Reference in New Issue
Block a user