This contains both the Helm charts and Packer configs that can be used to deploy a taskcluster installation onto Kubernetes. This is very much a work in progress, and is only being tried out on Minikube for the time being.
First set up a Minikube cluster and install Helm. Install Tiller with Helm init. Next yarn install.
To install onto a Kubernetes cluster, first copy user-config-example.yml to user-config.yml and then
yarn start. To make changes once it has been installed, you can
helm update -f generated-config.yml <release name> . where release name is the name of the release that was
created when you installed.
First install Packer and then from the packer directory,
packer build -var service=<github project name> ./templates/node.json. Where the github project is
in the taskcluster org. This currently only works with node services that use npm and run under node 7.
An image will be pushed to imbstack's docker hub and will immediately
be available for use in the Helm configuration.
Following is a non-exhaustive list of things I can think of that need to happen before this can work:
- Services that run inside this must have instances of hardcoded urls (i.e. taskcluster.net) removed
- taskcluster-client should be made to more easily work with Kubernetes routing
- All dependencies on Pulse should be removed and replaced with taskcluster-pulse
- Allow certain subsets of services to be disabled. e.g. sentrymanager in auth, lib-monitor support in most services, etc. This should be done with disable flags that can be set in config.yaml at install time to avoid needing creds.
- Allow publishing of docs/schemas to be turned off in an installation for anybody who is using straight tc without any modifications of their own.
- A script should be written that does all of the manual steps of install for you. This script is being pseudo-coded in src/main.js at the moment.
- This Helm chart should be pushed to a Helm repository with signing.