Datawire Infrastructure
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin
ci
dns
iam
kubernetes_clusters
public_keys
s3
.gitignore
.travis.yml
LICENSE
README.md
backend.tf
kops.tf
kubernetes_clusters.tf
main.tf
outputs.tf
requirements.txt

README.md

Datawire Infrastructure

Build Status

Join the chat at https://gitter.im/datawire/infrastructure

Core / common infrastructure definition and automation for Datawire's backend.

We are redoing this in the near future to be simpler and easier...

Cluster Management

  1. Create a branch for whatever work you're going to perform.
  2. export KOPS_STATE_STORE s3://datawire-kops-state
  3. export CLUSTER_NAME=prod or export CLUSTER_NAME=dev

Increase worker nodes

  1. Open kubernetes_clusters/$CLUSTER_NAME/kops/clusters.yaml
  2. Find the nodes InstanceGroup at the bottom of the file.
  3. Change minSize and maxSize as desired.
  4. Run kops replace -f kubernetes_clusters/$CLUSTER_NAME/kops/clusters.yaml
  5. Run kops update --name=${CLUSTER_NAME}.k736.net --target terraform --out kubernetes_clusters/dev/
  6. Commit changes and open a PR against master

Emergency skip CI

  1. After kops update ... run ci/terraform_plan.sh.
  2. Verify the plan does what you expect (ask Phil if you're unsure).
  3. Run ci/terraform_apply.sh.
  4. Commit changes back to master.

License

Licensed under Apache 2.0. Please read LICENSE for details.