Skip to content
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

Open
RJPercival opened this issue Nov 5, 2019 · 1 comment
Open

Fully declarative deployment configs for Google Cloud #1952

RJPercival opened this issue Nov 5, 2019 · 1 comment

Comments

@RJPercival
Copy link
Contributor

RJPercival commented Nov 5, 2019

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).

@RJPercival
Copy link
Contributor Author

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.

@paulmattei paulmattei moved this from Needs triage to Low priority in Trillian Mar 4, 2020
@paulmattei paulmattei moved this from Low priority to Backlog in Trillian Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Trillian
  
Backlog
Development

No branches or pull requests

2 participants