FAQ
Active development happens in the "dev" branch. If you have a contribution just create a PR to it.
Once you add the "ready-to-test" label, tests will automatically be kicked off. Our internal Jenkins instance is used to run the tests. The CI config for the project can be found at teapot/kubernetes-on-aws-e2e on our internal Github Enterprise.
We only support rolling out changes to our internal clusters so far. Our Kubernetes clusters are divided into multiple channels. Each channel has a corresponding branch. For example, the "alpha" branch represents the state of clusters in the "alpha" channel. See Cluster Provisioning to learn more. To roll out changes to a particular channel, create a PR to it's corresponding branch e.g dev-to-alpha. You may use the prepare-pr.sh script to create a PR.