Epic: Configurable K8s Clusters

[just-mitch]

Design

Tasks

Preview Give feedback

1. feat: basic helm chart #7999
   5 of 5
   +0
   
2. chore: CI support for ad-hoc k8s clusters #8000
   4 of 4
   +0
   
3. chore: network topology test matrix #8001
   2 of 4
   +0
   
4. chore: set up staging network #8004
   4 of 5
   +0
   
5. test: nightly KIND test #8506
   +0
   
6. infra: fix nightly KIND test #8831
   +0
7. infra: stable staging deployment #8822
   +0
8. infra: spartan passive test results #8828
   +0
9. infra: stress test passive node monitoring #8507
   +0
10. infra: spartan performance benchmarking #8006
    0 of 3
    +0
11. infra: chaos testing support #8002
    0 of 4
    +0
12. infra: spartan public network deployment #8005
    0 of 4
    +0
13. docs: spartan network user guide #8007
    0 of 5
    +0
14. test: p2p performance #8027
    +0
    
15. test: basic p2p resilience #8026
    0 of 4
    +0

[stevenplatt]

I have added staging and production branches to the repo.
The intention is to allow developers to graduate the codebase into different stages of public release using git.

In practice the merge flow would be:

• master --> staging --> production

This flow could make it easier to allocate categories of tests to different stages of release.

In practice test allocation would be:

• local: active development (fast feedback)
• master: per PR, nightly (normal feedback)
• staging: soak testing, early access (slow feedback)
• production: general availability (passive monitoring)

What do you think @spypsy @ludamad ?

[ludamad]

Seems reasonable :)