Private GKE with restricted access to cluster master endpoints
A guide to private Google Kubernetes Engine cluster with different level of restricted access to cluster master endpoints
Can I use Travis CI with Spinnaker?
Yes you can! Just like Jenkins, Spinnaker has a native integration with Travis. You can easily use it to trigger deployments once CI builds finish. However, unlike with Jenkins, you cannot use Travis to run arbitrary jobs. This is more of a limitation imposed by Travis than a limitation of Spinnaker itself.
Igor is the Spinnaker service responsible for interacting with external CI systems like Jenkins and Travis. So, in order to configure a Travis Master, you’ll need to add the following configuration to
travis: enabled: true # Travis names are prefixed with travis- inside igor. masters: - name: ci # This will show as travis-ci inside spinnaker. baseUrl: https://travis-ci.org address: https://api.travis-ci.org githubToken: a-github-token regexes: - /Upload https?:\/\/.+\/(.+\.(deb|rpm))/
You can configure multiple Travis masters by adding more entries under the
regexes key is used to parse build information out of the Travis build log using the
art CLI. This information is then used by Spinnaker pipelines to inform Bake stages which package versions should be installed during a bake stage.
Finally, in order to ensure that Igor is enabled, add the following to
services: igor: enabled: true