spingo | bash scripts to setup an enterprise-grade Spinnaker | GCP library

Navigate to https://github.com/homedepot/spingo/generate or click the green Use this template button above
Choose where you want to create your repo then clone it down Hint: You can clone the repo from Google Cloud Shell for faster access to the Google APIs but you must have access to a Vault server to store/read the configuration info
Inside your clone of your repo run the following command: ./quickstart.sh
When asked to enter your Google OAuth credentials use these instructions
When asked to enter your Slack token use these instructions if you choose to setup Slack notifications or choose the option for No
When you see Quickstart complete you should see a Terraform output variable called halyard_command which you can copy to log into your ephemerial halyard VM You should wait about 20 seconds or so for the VM to be up and running and ready to take commands before logging into it
Log into the halyard VM
Run the showlog command to follow the setup process by watching the tailing of the logs that setup all of the dependencies needed for all of the scripts inside the quickstart script If you selected to auto run halyard quickstart during the initial quickstart then your Spinnaker should already be being setup Once you see Autostart complete please log into your Spinnaker deployment(s) you can close out of showlog by pressing ctrl-c If you selected to NOT auto run halyard quickstart then after you see setup complete you can close out of showlog by pressing ctrl-c
Run the spingo command to sudo into the shared user account If you selected to NOT auto run halyard then after you see a user prompt like this spinnaker@halyard-thd-spinnaker:~$ you will either need to run ./quickstart.sh or run each of the pre-populated scripts that the ./quickstart script is configured to run in that order
Once all the scripts are completed you should be able to log into Spinnaker and visit the workloads page inside the Google Cloud Console and see all the Spinnaker kubernetes deployments by cluster
Follow the instructions here to setup basic monitoring and alerting of the Spinnaker deployments.
After the managed DNS is setup you will need to direct the DNS hostname to the proper nameservers. After the DNS directory is run by quickstart, Terraform will output the new nameservers on the screen called google_dns_managed_zone_nameservers = [ "ns-cloud-c1.googledomains.com.", "ns-cloud-c2.googledomains.com.", ...]. You then need to log into your domain hosting provider and direct the owned domain to all four of these name servers so that traffic can be routed to your project and SSL certificates can be requested through the Let's Encrypt Google domain authentication plugin which adds a TXT record to the domain to prove that it is owned by you. Once Google Cloud DNS is properly getting traffic you will be able to complete the Let's Encrypt SSL configuration.