-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fully declarative deployment configs for Google Cloud #1952
Labels
Comments
2 tasks
2 tasks
2 tasks
We now have a Terraform config for deploying Trillian to GCP with a Cloud Spanner database. However, it's still necessary to use the shell scripts if you want to use a MySQL database instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our deployment process currently involves running shell scripts in examples/deployment/kubernetes, which use a combination of tools to build Docker images, setup a Kubernetes cluster on GCP, configure it and deploy Trillian. This could be improved by using a tool such as Terraform to replace the shell scripts and either relying on our published Docker images or using Google Cloud Build to create the images. Kustomize could be used to support a wider variety of deployments (currently, we use envsubst for a similar purpose, but it is less flexible).
The text was updated successfully, but these errors were encountered: