Context
The zaino CI pipeline now publishes Docker images to zingolabs/zainod (and zingolabs/zaino for backwards compat). Our deployments still reference the old zingodevops/zaino repository.
What needs to change
clusters/production/values/golden-mainnet.yaml — zaino.image.repositoryclusters/production/values/golden-testnet.yaml — zaino.image.repositoryclusters/local/values/golden-mainnet.yaml — zaino.image.repositoryclusters/local/values/golden-testnet.yaml — zaino.image.repositoryplatform/argo-workflows/workflows/serve-zaino.yaml — default registry parameterplatform/argo-workflows/workflows/ephemeral-values.yaml — image references- Any other references to
zingodevops/zaino
Notes
- The old
zingodevops/zaino repo still receives images for now, so this is not urgent
- Should be coordinated with the next stable release to avoid confusion
- Verify
zingolabs/zainod has the same DockerHub credentials/access configured in the cluster's docker-registry-creds secret
Context
The zaino CI pipeline now publishes Docker images to
zingolabs/zainod(andzingolabs/zainofor backwards compat). Our deployments still reference the oldzingodevops/zainorepository.What needs to change
clusters/production/values/golden-mainnet.yaml—zaino.image.repositoryclusters/production/values/golden-testnet.yaml—zaino.image.repositoryclusters/local/values/golden-mainnet.yaml—zaino.image.repositoryclusters/local/values/golden-testnet.yaml—zaino.image.repositoryplatform/argo-workflows/workflows/serve-zaino.yaml— defaultregistryparameterplatform/argo-workflows/workflows/ephemeral-values.yaml— image referenceszingodevops/zainoNotes
zingodevops/zainorepo still receives images for now, so this is not urgentzingolabs/zainodhas the same DockerHub credentials/access configured in the cluster'sdocker-registry-credssecret