We have testing to do in order to feel confident about a 2.3 release.

• Manual testing
  • Cloud-provider test script #2516 Mutli-cloud (AKS, EKS, GKE, DO)
    • Manual script to validate identity and auto inject
    • Run integration tests
  • Introduce ServiceProfile test plan #2518 Introduce test plan for service profiles
    • Service profiles integration tests #2638 introduce integration tests
    • add service profile integration tests for service profile metrics #2685 service profile metrics
  • Test script to deploy emojivoto and books at scale #2517 Emojivoto / books
    • identity (TLS)
    • more than 100 replicas
    • vote-bot/traffic at 1k rps
    • Run with more than 100 services, all with service profiles (copy emoijvoto)
      • increase replicas
      • increase namespaces
  • Introduce test-scale script #2578 Use the lifecycle environment to test service discovery and caching
• Soak for a week
  • solicit the community for edge release input, via tweets/slack
• Automated testing
  • Identity (current tests w/ TLS)
    • Once part of default install, integration tests will do some validation automatically
    • Identity integration tests #2519 Modify existing TLS integration tests to perform additional validation, via metrics, etc
    • proxy: Integration tests for identity #2505 Proxy integration tests
    • controller/identity unit tests (Introduce the Identity controller implementation #2521 (review))
  • Introduce ServiceProfile integration tests #2520 Add service profile integration tests
  • Injection integration tests
    • Introduce auto inject integration tests #2595 with and without --proxy-auto-inject
    • Introduce inject integration tests #2616 cli inject integration tests
    • cli inject with and without auto inject
    • Introduce inject integration tests #2616 pod deploys and deployment deploys
    • Introduce inject integration tests #2616 linkerd.io/inject: enabled, linkerd.io/inject: disabled, and no annotation present
    • Introduce inject integration tests #2616 pod annotations and deployment annotations
    • creating and updating
  • linkerd upgrade (cli: Introduce an upgrade command #2564 (comment))
    • upgrade command unit tests #2637 unit tests
      • Introduce upgrade command unit tests #2639 input/output unit tests
      • upgrade: unit tests #2672 individual function unit tests / refactor
    • upgrade integration tests #2669 integration tests

Also this needs to be turned into a test plan doc / checklist that is checked into the repo so that we do this work before any stable releases.