AUTHORIZER IMAGE UPDATE

In a Kubernetes cluster, updating authorizer image entails either a straightforward image update or a more involved "cleandb" deployment.

Authorizer Image Update GitHub Action - https://github.com/0chain/zus-cicd/actions/workflows/authorizer-image-update.yaml

INTRODUCTION

In a Kubernetes deployment, updating the image is a standard procedure to deliver new application versions or updates. While a "cleandb" deployment via Helm entails wiping the slate clean for major upgrades or a fresh start, it also resets configurations and databases.

DOCKERHUB

• authorizer image tags - https://hub.docker.com/r/0chaindev/authorizer/tags

Authorizer Image Update - CleanDB

It requires 4 inputs -

1. Enter yes for cleandb deployment of Authorizer.

2. Enter Name of the Network like demo, test, etc.

3. Enter Network Domain Name like 0chain.net, zus.network, etc.

4. Enter the Authorizer Image Tag

Authorizer Image Update - Without CleanDB

It requires 4 inputs -

1. Enter no for cleandb deployment of Authorizer.

2. Enter Name of the Network like demo, test, etc.

3. Enter Network Domain Name like 0chain.net, zus.network, etc.

4. Enter the Authorizer Image Tag

A "cleandb" deployment using Helm gives a complete solution, essential for substantial configuration changes and clean deployments, while upgrading images in Kubernetes enables the easy integration of new versions.