A broader collection of documentation around how to use DevNet.
DevNet refers to a set of blockchain protocol actors within the Pocket Network (POKT) that are deployed on a Kubernetes cluster. This platform is utilized for testing, developing, deploying, and releasing Pocket V1 code.
Some tests may be too resource-intensive to perform on your own machine. Additionally, running tests in a clean, standardized environment can help to identify elusive errors and uncover unintended or secondary effects of code changes. Migrations, in particular, often reveal issues in such test environments.
<aside> 💡 Prerequisites You will need to follow this guide for DevNet access and credentials.
</aside>
argo auth tokenDevNet operates within a Kubernetes environment. It leverages ArgoCD, Argo Workflows, and GitHub Actions to enable streamlined testing and development.
ArgoCD is utilized to maintain the desired state of the Kubernetes cluster based on definitions in the Git repository.
When a e2e-devnet-test label is added to a Pull Request (PR), a new DevNet is deployed, a build is initiated to create container images, and end-to-end (e2e) tests are run using Argo Workflows.
Once you have credentials mentioned in the prerequisites section, it’s recommended to use k9s to work with DevNet.
DevNets are built out of Helm charts. Helm charts are basically Go templates applied to Kubernetes manifests to make scripting and mild processing of Kubernetes manifests easier. Here is an example of a very simple DevNet containing 4 validators: