Page History

...

1. • kubeadm-bootstrap and kubeadm-terraform
2. Roll versions forward
   1. ndslabs
      1. gui/swagger.yaml: NDS Labs swagger API spec version number
      2. apiserver/build.sh: NDS Labs API Server Docker image version tag
      3. gui/Dockerfile: NDS Labs UI / webserver Docker image version tag
      4. gui/package.json: NDS Labs UI  / webserver NPM package version number
      5. gui/ConfigModule.js: NDS Labs UI Angular app build version number
   2. workbench-helm-chart
      1. values.yaml: NDS Labs API Server + UI Docker image version tags
   3. kubeadm-bootstrap
      1. install-kubeadm.bash: Kubernetes / Docker version numbers
      2. init-master.bash: Helm version numbers
   4. kubeadm-terraform
      1. kubeadm-bootstrap git release/tag: assets/bootstrap.sh
3. PR from release branch to master
   1. Thorough testing, then more testing, then merge to master
4. Tag master with new version number (freshly tested and stable)
   1. Any new merges and tags will trigger new Docker images to be builtFix any errors and run
5. Wait for newly-tagged resources to automatically finish building and pushing Docker images
   1. Run a quick smoke test with newly-tagged resources
   2. Fix any last-minute errors directly on master and recreate release
6. Backport any missing changes from master into develop
   1. This should include, at the very least, rolling forward to new version numbers

...