TEST NETWORK DEPLOYMENT

test.zus.network - Using a Kubernetes-based deployment and an internal Helm chart for effective setup and administration, the network is set up for developer testing.

INTRODUCTION

The network has been set up expressly to meet developer's testing needs. It uses a Helm chart internally and runs on Kubernetes-based infrastructure. Developers can test Blockchain Network & their apps in a managed and controlled environment through Helm's fast deployment, version control, and configuration management, Kubernetes effective orchestration, and scaling.

Test Network GitHub Action - https://github.com/0chain/zus-cicd/actions/workflows/test.zus.network.yaml

GITHUB ACTION WITH HELM CHART

The construction, personalization, and execution of workflows within a GitHub repository are all made possible via the automation platform known as GitHub Actions. It facilitates activities like continuous integration, deployment, and several automated procedures to simplify development workflows and enhance team cooperation.

Helm charts are used by GitHub Action to simplify Kubernetes deployment. This integration automates the deployment process, improving efficiency and consistency while also allowing for version-controlled, predictable, and scalable application administration within Kubernetes clusters.

These repositories are used by Zus team to provide well-maintained, dependable base images for efficient containerization.

0chaindev docker hub repository - https://hub.docker.com/u/0chaindev

HELM CHART

Helm Chart Documentation - https://app.gitbook.com/o/-MWVD-8BJlEUSju1kMMq/s/D7ZE2euEA7yyBkf7stt9/~/changes/48/0helm-repo

Helm charts are preconfigured Kubernetes resource bundles that simplify the deployment, scaling, and maintenance of complicated applications. They make application packaging and sharing more efficient inside the Kubernetes ecosystem by streamlining installation, upgrades, and rollback processes, providing version control, and parameter customization.

GITHUB REPOSITORIES

zwalletcli - https://github.com/0chain/zwalletcli

zboxcli - https://github.com/0chain/zboxcli

web-apps - https://github.com/0chain/web-apps

GITHUB ACTION TRIGGER

The git-action for test.zus.network requires 8 inputs -

  1. 0chain image tag [ miner & sharder image tag ]

  2. blobber image tag [ blobber & validator image tag ]

  3. 0dns image tag

  4. 0box image tag

  5. authorizer image tag

  6. zs3server image tag

  7. zwalletcli branch

  8. zboxcli branch

Also if your branch name is other than main then select your branch from Use workflow from and give inputs, then click on Run WorkFlow.

NOTE - it will do cleanDB deployment

  • https://test.zus.network/sharder01/_diagnostics

  • https://test.zus.network/miner01/_diagnostics

  • https://test.zus.network/blobber01/

  • https://test.zus.network/validator01/

  • https://test.zus.network/authorizer01/

  • https://test.zus.network/dns/

  • https://0box.test.zus.network/

  • https://rancher.test.zus.network/

  • https://grafana.test.zus.network/

NOTE

This Network is deprecated however if you wish to setup it again then just setup k8s cluster & keys on a server by using Zprem repository & setup Github Runner.

Last updated