Release notes - Zenko - Version 2.0.0-rc.3

Bug

ZENKO-3547 Upgrade zenko-operator to satisfy web browser https security policy on zenko-ui

ZENKO-3424 Change metrics collector to not try and use cloudwatch

Release notes - Zenko - Version 2.0.0-rc.2

Bug

ZENKO-3477 Disable lifecycle expiration, transition, and ingestion on Zenko

ZENKO-3458 List users shows users from all accounts

ZENKO-3457 Config updates take longer than UI shows

ZENKO-3441 Remove default fallback s3 endpoint

Improvement

ZENKO-3496 Send a not implemented error for IAM calls not supported on MongoDB

ZENKO-3494 Add logout option when request unauthorized on Zenko UI

ZENKO-3474 Test IAM root user access keys redux actions

ZENKO-3473 Handle IAM errors on Zenko UI

Release notes - Zenko - Version 2.0.0-rc.1

Documentation

ZENKO-3377 Document creating, updating and deleting a replication workflow in Zenko-ui

Feature

ZENKO-3455 Upgrade zenko ui version to 0.6.0

ZENKO-3443 Upgrade pensieve-api/zenko-operator for initial overlay seed

Improvement

ZENKO-3361 Enhance UX on Bucket and Data Browser

Story

ZENKO-3439 Ability to create root user access keys on zenko-ui

ZENKO-3283 Ability to read and delete root user access keys on zenko-ui

Release notes - Zenko - Version 2.0.0-alpha.8

Bug

ZENKO-3429 Upgrade backbeat to latest release

Feature

ZENKO-3435 Bump Zenko to 2.0.0-alpha.8

ZENKO-3433 Bump zenko UI version

Improvement

ZENKO-3434 Zenko-Operator: change Buckets to Data Browser

ZENKO-3418 Use the correct icon for entities in the Empty state creation

ZENKO-3409 Remove quota feature in Storage Location Edition

ZENKO-3406 Account properties tab width

ZENKO-3355 Enhance UX on Replication GUI

ZENKO-3137 Update zenkoversion.yaml/imagePullPolicy for production usage

Story

ZENKO-3369 embed md5 in iso

Release notes - Zenko - Version 2.0.0-alpha.7

Feature

ZENKO-3426 Bump Zenko to 2.0.0-alpha.7

ZENKO-3375 Replication endpoints for API

ZENKO-3368 Dual auth: static file+vault

Improvement

ZENKO-3391 Enhance UX Final (Account list & Data Browsing)

ZENKO-3382 Updating go-swagger to v0.27.0

ZENKO-3372 XDM-UI - Rebranding UX improvements

ZENKO-3179 "Copy" icons to add

ZENKO-3178 "Delete Account" button to move to properties tab

Release notes - Zenko - Version 2.0.0-alpha.6

Bug

ZENKO-3393 Allow CreateAccessKey on account with AssumeRoleWWI Credentials

ZENKO-3392 Allow DeleteAccessKey on account with AssumeRoleWWI Credentials

ZENKO-3388 ListAccessKeys doesn't respect marker generated via AWS-CLI

ZENKO-3387 Allow ListAccessKeys on account with AssumeRoleWWI Credentials

Feature

ZENKO-3425 Release 2.0.0-alpha.6

ZENKO-3423 Update pensieve-api

ZENKO-3381 Expose Vault Admin/IAM API service over ingress. Port: 8600

Story

ZENKO-3360 AWS Replication policy transformer

Changelog

Known issue

• Cosmos operator can occasionally fail to create the necessary resources for out-of-band ingestion workflows. This error occurs when the hash used for the label version-hash consists solely of numbers.

Improvements

• update charts to be compatible with Kubernetes 1.18
• updates Cloudserver global agent to use freeSocket.Timeout
• adds Backbeat prometheus metrics exporter over http
• adds Backbeat flag to force the transition workflow to trigger 1 day earlier

Bugfixes:

• fixes Cloudserver issue in which Orbit instance registration requests fails
• fixes Cloudserver issue in which the Azure complete mpu API prematurely completes on a failed part
• fixes S3Utils issue in which the retry_pending cronjob will fail due to out of memory

Pre-install

helm dependency update

Install

The following command can be used to install a 3 node Zenko 1.2.2

helm install https://github.com/scality/Zenko/releases/download/1.2.2/zenko-helm-chart-1.2.2.tgz

The following command can be used to install a 5 node Zenko 1.2.2

helm install https://github.com/scality/Zenko/releases/download/1.2.2/zenko-helm-chart-1.2.2+5.tgz

For more complex installations please follow the instructions here

Upgrading

The following commands assumes that your release name is zenko.

If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

To upgrade basic 3 node installs use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag

helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.2.2/zenko-helm-chart-1.2.2.tgz

NOTE if you installed using the 5 node package, be sure to use that for your upgrades as well

Changelog

Known issue with new installs

The is a bug preventing new installs on 1.2.1. We are working on a patch and will be released soon. The suggested workaround right now is to install 1.2.0 and upgrade to 1.2.1.

Improvements

• Add options to the chart templates to pass arbitrary selector maps, matching PVs to PVCs on setup
• Add tunable to set concurrency for asynchronous replication tasks

Bugfixes:

• Fixes leaking TCP sockets when clients abort connections during transfer to S3 compatible locations
• Fixes objects ingested via OOB updates from S3C which were not searchable as tags were not serialized properly
• Fixes objects with . (dot) and $ (dollar) in their metadata which were not escaped correctly leading to search issues
• Fixes an issue of overindentation in ingress chart that breaks manual tls config

Pre-install

helm dependency update

Install

The following command can be used to install a 3 node Zenko 1.2.1

helm install https://github.com/scality/Zenko/releases/download/1.2.1/zenko-helm-chart-1.2.1.tgz

The following command can be used to install a 5 node Zenko 1.2.1

helm install https://github.com/scality/Zenko/releases/download/1.2.0/zenko-helm-chart-1.2.1+5.tgz

For more complex installations please follow the instructions here

Upgrading

The following commands assumes that your release name is zenko.

If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

To upgrade basic 3 node installs use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag

helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.2.1/zenko-helm-chart-1.2.1.tgz

NOTE if you installed using the 5 node package, be sure to use that for your upgrades as well

Changelog

This is a maintenance release. For latest features please install 1.2.0

Fixes:

• Replication and Lifecycle features
  • Expose the "concurrency" tunable of the backbeat data processor and status processor through an environment variable,
    so that it can be changed from Zenko charts.

NOTES

Install

• Use the following command to install a 3-node Zenko 1.1:

  helm install https://github.com/scality/Zenko/releases/download/1.1.10/zenko-helm-chart-1.1.10.tgz
  

• For more detailed install steps, follow the instructions here.

Upgrading

The following commands assume that your release name is named zenko.

• If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

• To upgrade basic three-node installs, use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag.

  helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.1.10/zenko-helm-chart-1.1.10.tgz
  

• Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Follow the instructions outlined here for more information.

Zenko

A full changelog for Backbeat can be found below.

Backbeat

A full changelog can be found here.

Changelog

Features:

• Out of Band updates from AWS S3
• Backups for MongoDB, Zookeeper services
• Bucket Policies to allow cross-account access

Requirement changes

• Charts have been updated to support MetalK8s 2.5.0 (Kubernetes 1.16)
• Supports helm ~2.16.0

Pre-install

helm dependency update

This brings the newly added charts for Blobserver cert-manager-crds, cert-manager from the chart repositories.

Install

The following command can be used to install a 3 node Zenko 1.2.0

helm install https://github.com/scality/Zenko/releases/download/1.2.0/zenko-helm-chart-1.2.0.tgz

The following command can be used to install a 5 node Zenko 1.2.0

helm install https://github.com/scality/Zenko/releases/download/1.2.0/zenko-helm-chart-1.2.0+5.tgz

For more complex installations please follow the instructions here

Upgrading

The following commands assumes that your release name is zenko.

If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

To upgrade basic 3 node installs use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag

helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.2.0/zenko-helm-chart-1.2.0.tgz

NOTE if you installed using the 5 node package, be sure to use that for your upgrades as well

Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Please follow the instructions outlined here for more information.

Changelog

Features:

Requirement changes

Install

The following command can be used to install a 3 node Zenko 1.2

helm install https://github.com/scality/Zenko/releases/download/1.2.0-rc.4/zenko-helm-chart-1.2.0-rc.4.tgz

The following command can be used to install a 5 node Zenko 1.2

helm install https://github.com/scality/Zenko/releases/download/1.2.0-rc.4/zenko-helm-chart-1.2.0-rc.4+5.node.tgz

For more complex installations please follow the instructions here

Upgrading

The following commands assumes that your release name is zenko.

If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

To upgrade basic 3 node installs use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag

helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.2.0-rc.4/zenko-helm-chart-1.2.0-rc.4.tgz

NOTE if you installed using the 5 node package, be sure to use that for your upgrades as well

Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Please follow the instructions outlined here for more information.

Zenko

Full changelog for Backbeat and Cloudserver can be found below

Changelog

Fixes:

• Out of Band (OOB) updates from S3 Connector

  • Revert of the change that addresses issues of pausing from Orbit due to unintended regression
  • Fixes an issue where tagging updates on objects in S3 Connector were not received in Zenko

• S3Utils

  • Fixes a bug in CRR Existing Objects script where the script halts when there is an error making a request to Metadata

NOTES

Install

• Use the following command to install a 3-node Zenko 1.1:

  helm install https://github.com/scality/Zenko/releases/download/1.1.9/zenko-helm-chart-1.1.9.tgz
  

• For more detailed install steps, follow the instructions here.

Upgrading

The following commands assume that your release name is named zenko.

• If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

• To upgrade basic three-node installs, use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag.

  helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.1.9/zenko-helm-chart-1.1.9.tgz
  

• Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Follow the instructions outlined here for more information.

Zenko

A full changelog for Backbeat and Cloudserver can be found below.

Cloudserver

A full changelog can be found here

Backbeat

A full changelog can be found here.

Changelog

Fixes:

• Out of Band (OOB) updates from S3 Connector

  • Addresses issues of pausing from Orbit
  • Fixes an issue where tagging updates on objects in S3 Connector were not received in Zenko

• S3Utils

  • Fixes a bug in CRR Existing Objects script where the script halts when there is an error making a request to Metadata

NOTES

Install

• Use the following command to install a 3-node Zenko 1.1:

  helm install https://github.com/scality/Zenko/releases/download/1.1.8/zenko-helm-chart-1.1.8.tgz
  

• For more detailed install steps, follow the instructions here.

Upgrading

The following commands assume that your release name is named zenko.

• If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

• To upgrade basic three-node installs, use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag.

  helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.1.8/zenko-helm-chart-1.1.8.tgz
  

• Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Follow the instructions outlined here for more information.

Zenko

A full changelog for Backbeat and Cloudserver can be found below.

Cloudserver

A full changelog can be found here

Backbeat

A full changelog can be found here.

This release contains a work in progress optimization for replicating non-mpu objects specifically to an S3 compatible location.
For production installs, please use 1.1.7, our latest GA release.

Install

helm install https://github.com/scality/Zenko/releases/download/1.1.8-beta/zenko-helm-chart-1.1.8-beta.tgz

Upgrade

helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.1.8-beta/zenko-helm-chart-1.1.8-beta.tgz

Changelog

Improvements:
This release carries no new Zenko chart improvements
Fixes:
This release carries no new Zenko chart bug fixes

NOTES

Requirement changes

• The operator features in Zenko 1.1 require Kubernetes version 1.11.3 or newer to install.
• Zenko 1.1 upgrades MongoDB to version 3.6. Due to this change, not all features will be enabled by default when upgrading from 1.0. Read post-upgrade instructions here.

Install

• Use the following command to install a three-node Zenko 1.1:

  helm install https://github.com/scality/Zenko/releases/download/1.1.7/zenko-helm-chart-1.1.7.tgz
  

• For more complex installations, follow the instructions here.

Upgrading

The following commands assume that your release name is named zenko.

• If you used custom values to install then those same values must be specified on upgrade. You can see the custom values of a running deployment with $ helm get values zenko > my-configuration.yaml

• To upgrade basic three-node installs, use the below command. More complex installs will likely need to specify a custom values file with the -f my-configuration.yaml flag.

  helm upgrade zenko https://github.com/scality/Zenko/releases/download/1.1.7/zenko-helm-chart-1.1.7.tgz
  

• Upgrading from 1.0.x requires minor post-upgrade steps to enable the full feature set available in this version. Follow the instructions outlined here for more information.

Zenko

A full changelog for Backbeat and Cloudserver can be found below.

Cloudserver

A full changelog can be found here

Backbeat

A full changelog can be found here.