Introduction

We at Celestia understand that testground's primary focus is Kubernetes as the execution environment for testing and benchmarking distributed systems, given its robustness, scalability, and extensive features for managing resources, scaling applications, and automating deployment and management tasks.

This decision to go all in K8s is supported by Celestia's success with:

• regression, release, stress testing of large scale network
• load testing of various infrastructures.

Plan

For 2023, we aim to implement:

• different tools for metrics/traces/logs collection/analysis
• CI/CD readiness, and seamless installation.

What we will do in upcoming week:

• Cut a release as is to snapshot amazing work done in 2022
  • This will give the community members a snapshot of what is working as expected
  • Thus let us move forward with piece-of-mind

What we start doing timeline for 2023

• Refactor bash scripts setup to infrastructure as code:
  • Rewrite the setup scripts to use tools like Terraform, ArgoCD to provision and configure the infrastructure needed for running Testground tests.
  • Document the new setup process in AWS.
  • More info here [EPIC]: Testground's Infrastructure as Code celestiaorg/test-infra#147
• Testground daemon improvements:
  • Every test run should sit in its namespace in the Kubernetes cluster:
    • Update the Testground runner to create a separate Kubernetes namespace for each test run, to isolate the test environment and avoid conflicts between different tests.
    • Add support for automatically cleaning up the test namespace after the test run is completed, to avoid resource leaks and reduce clutter in the cluster.
  • Integrate the daemon with CI/CD pipelines, such as GitHub Actions.
    • Document how this can be achieved