Platform stability in release process

[thomasvincent]

Platform Stability

Each platform is marked as either pre-alpha, alpha, beta, or stable. This document outlines the rough criteria for each.

Pre-Alpha

Requirements

• Initial static Terraform assets are added to this repo and undergoing active development
• No installer integration

Packaging

• None

User Flow

Development workflows only

Alpha

• Manually tested and can reliably produce minimally functioning clusters
  • Kuberntes API works
  • Marathon API works

Packaging

• Assets are packaged into native platform format, docker, and tarballs.

User Flow

1. Manually create terraform.tfvars file
2. Use static Terraform assets contained in installer tarball
3. Manually run Terraform

Travis Only

1. Use travis to provision cluster

Beta

Requirements

• Best practices for platform implemented
  • Network security
  • Automated testing results are published
  • DNS & Load Balancing
  • Generates HA / Multi-AZ infrastructure
• Automated testing results are published
  • Kubernetes e2e and conformance tests pass (TBD)
  • Marathon e2e and conformance tests pass (TBD)
  • Smoke tests work
• Cloud Provider enabled for the platform
• Test updating and migration from previous version
• README documents all customizations
• Two documented platform users

Packaging

• Assets are packaged into native platform format, docker, and tarballs.

User Flow

1. Generate terraform.tfvars file, or manually create it.
2. Use static Terraform assets contained in installer tarball
3. Manually run terraform

Travis Only

1. Use travis to provision cluster

Stable

Requirements

• Automated tests pass for all supported releases
• Tectonic Installer UI for platform (optional)

Packaging

• Assets are packaged into native platform format, docker, and tarballs.

User Flow

Travis Only

1. Use travis to provision cluster

Non-GUI

1. Manually create terraform.tfvars file
2. Use static Terraform assets contained in installer tarball
3. Manually run Terraform

[Theaxiom]

👍