Bot releases are visible (Hide)

Zenko - V1.1.5 Patch Release

Published by rahulreddy over 4 years ago

Changelog

Fixes:

OOB S3C- Ingestion producer should not wait between batches if raft log has not been fully consumed

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.5/zenko-helm-chart-1.1.5.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.5/zenko-helm-chart-1.1.5.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

No new changes from the previous patch release

Backbeat

A full changelog can be found here.

Zenko - V1.1.4 Patch Release

Published by ssalaues almost 5 years ago

Changelog

Fixes:

Fixes prometheus metrics reporting in Cloudserver
Update Zenko overview dashboard with relevant information
- Ingress/Egress live bandwidth
- Throughput by operation type (PUT,GET,DELETE)
- Throughput of Rclone based ingestion
- Cloudserver CPU consumption per node
Fixes cron job deadlines
Increase the JVM max heap size for Kafka to 6GB (previously 1GB)

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.4/zenko-helm-chart-1.1.4.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.4/zenko-helm-chart-1.1.4.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.

Zenko - Zenko 1.2.0-rc.2

Published by ssalaues almost 5 years ago

Changelog

Features:

Bucket Policies
Out-of-Band (OOB) updates from AWS and Ceph
- OOB locations now start in a paused state
Backups for MongoDB (Zenko metadata layer) and Zenko Quorum (Zookeeper)

NOTES

This is a release candidate for Zenko 1.2.0. If you encounter any issues, please open a GitHub issue or post in the forums.

Requirement changes

Backups will require two additional PersistentVolume (PV). If you do not provision additional PVs then some pods may stay in a Pending status.

Install

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

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

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

helm install https://github.com/scality/Zenko/releases/download/1.2.0-rc.2/zenko-helm-chart-1.2.0-rc.2+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.2/zenko-helm-chart-1.2.0-rc.2.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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - Zenko 1.2.0-rc.1

Published by ssalaues about 5 years ago

Changelog

Features:

Bucket Policies
Out-of-Band (OOB) updates from AWS and Ceph
Backups for MongoDB (Zenko metadata layer) and Zenko Quorum (Zookeeper)

NOTES

This is the first release candidate for Zenko 1.2.0. If you encounter any issues, please open a GitHub issue or post in the forums.

Requirement changes

Backups will require two additional PersistentVolume (PV). If you do not provision additional PVs then some pods may stay in a Pending status.

Install

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

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

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

helm install https://github.com/scality/Zenko/releases/download/1.2.0-rc.1/zenko-helm-chart-1.2.0-rc.1+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.1/zenko-helm-chart-1.2.0-rc.1.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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - V1.1.3 Patch Release

Published by rahulreddy about 5 years ago

Changelog

Fixes:

Bug in Cloudserver that orphaned keys in sproxyd (https://github.com/scality/cloudserver/pull/2046)

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.3/zenko-helm-chart-1.1.3.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.3/zenko-helm-chart-1.1.3.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.

Zenko - V1.1.2 Patch Release

Published by rahulreddy about 5 years ago

Changelog

Fixes:

Bug in cosmos chart that caused the configured location to be configured globally per instance (https://github.com/scality/Zenko/pull/805)
Missing SSL certificates from the RClone image (https://github.com/scality/Zenko/pull/805)
Race conditions in Cosmos scheduler resulting in inconsistent OOB NFS deployment behavior (https://github.com/scality/Zenko/pull/792)
Bug in Backbeat that caused issues with OOB objects that were missing location info (https://github.com/scality/backbeat/pull/754)

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.2/zenko-helm-chart-1.1.2.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.1.2/zenko-helm-chart-1.1.2.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.1 Patch Release

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.1/zenko-helm-chart-1.1.1.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.1.1/zenko-helm-chart-1.1.1.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0 General Availability

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.0/zenko-helm-chart-1.1.0.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.1.0/zenko-helm-chart-1.1.0.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0-rc.5

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.0-rc.5/zenko-helm-chart-1.1.0-rc.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.1.0-rc.5/zenko-helm-chart-1.1.0-rc.5.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0-rc.4

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.0-rc.4/zenko-helm-chart-1.1.0-rc.4.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.1.0-rc.4/zenko-helm-chart-1.1.0-rc.4.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0-rc.3

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

helm install https://github.com/scality/Zenko/releases/download/1.1.0-rc.3/zenko-helm-chart-1.1.0-rc.3.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.1.0-rc.3/zenko-helm-chart-1.1.0-rc.3.tgz
```
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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0-rc.2

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

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

For more complex installations please follow the instructions here

Upgrading

The following command can be used to upgrade and assumes that your release name is zenko

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

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

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.1.0-rc.1

Published by ssalaues over 5 years ago

Changelog

NOTES

Requirement changes

The operator features in Zenko 1.1 requires 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 please read the info on post-upgrade instructions here

Install

The following command can be used to install Zenko 1.1

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

Upgrading

The following command can be used to upgrade and assumes that your release name is zenko

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

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 can be found here

Cloudserver

Full changelog can be found here

Backbeat

Full changelog can be found here

Zenko - v1.0.2-hotfix.1

Published by ssalaues over 5 years ago

Changelog

NOTES

This fixes an issue where Ring storage locations using HTTPS were not being parsed correctly by Cloudserver which resulted in failure to read or write from these locations.

The following command can be used to upgrade and assumes that your release name is zenko
```
helm upgrade zenko <path-to-Zenko>/Zenko/kubernetes/zenko 
```

Zenko

chore: bump cloudserver to 8.0.21
Improved documentation

Cloudserver

bugfix: ZENKO-1365 Orbit set https for RING+S3
The full Cloudserver Changelog changes can be found here

Zenko - v1.0.2

Published by giacomoguiulfo almost 6 years ago

Changelog

NOTES

There have been sporadic failures of large objects when writing to AWS due to socket hangups in the environment. This patch delivers customer configurable httpAgent options for external backends. Persistent HTTP connections are disabled for AWS by default. Currently, only AWS and GCP are supported. This configuration will be applied globally for all locations of the same type of external backend. In full transparency, please note occasional socket hangups may still be seen.
During internal testing, few objects were observed to get re-queued more than once. This did not have a measurable performance impact but was still perceived as pretty annoying. This issue has also been fixed and tested in this patch.

The following command can be used to upgrade and assumes that your release name is zenko
```
helm upgrade zenko <path-to-Zenko>/Zenko/kubernetes/zenko 
```

Zenko

chore: bump cloudserver to 8.0.20
improvement: ZENKO-1291 keepalive configuration for ext backends

Cloudserver

improvement: ZENKO-1291 disable keepAlive for AWS
improvement: ZENKO-1291 configurable httpAgent options
improvement: parse and include gcp request id on errors

Backbeat

ft: ZENKO-1175 tailable cursor to consume mongo oplog

Zenko - v1.0.1

Published by ssalaues almost 6 years ago

Changelog

NOTES

Improved documentation
Updated Cloudserver image
- Improved request ID logging for Azure and AWS (not GCP)
- User-agent tagging on Azure and GCP
The following command can be used to upgrade and assumes that your release name is zenko
```
helm upgrade zenko <path-to-Zenko>/Zenko/kubernetes/zenko 
```

Fixes included from 1.0.0-hotfix.1

Fixes to overspawning of zenko-queue-config pods
Added debug and maintenance tools
- Debug pods can be enabled with --set debug.enabled=true or through the values
- Maintenance options can be enabled/configure here

Merges

cloudserver: bump image
improvement: setting stage for documentation and william edits
Merge branch 'development/1.0' into improvement/doc-ZENKO-1206-5
docs: Manual patch improvement/doc-ZENKO-1206 cause history too big
Merge branch 'improvement/debug-pods' into q/1.0
ci: mark flaky gcp replication tests ZENKO-1277
[chore] update image version
ft: listv2 e2e tests
[chore] cloudserver test folder
improvement: switch debug tools to deployments
improvement: template common names and labels

Zenko - 1.0.0

Published by ssalaues about 6 years ago

Changelog

NOTES

Partitions and replicationfactor in zenko-queue (Kafka) topics can now be reconfigured/tuned post install
- Due to these changes, you may see a zenko-queue-configpod which handles the topic creation/updates
- This is created by a kubernetes job that will run until it reaches a Completed state
- In some cases, if your zenko-queue is not fully operational or not yet stabilized you may see a version of the pod in a Failed state. This is normal and the job will retry until it is successful.
- Any Failed or Completed pods can be safely deleted

Known Upgrade issues

Upgrading from older versions of the kubernetes Zenko stack requires specific values that can be set at install time. These values were changed to provide safer install defaults.
- The following command can be used to upgrade and assumes that your release name is zenko
```
helm upgrade zenko ./zenko \
--set s3-data.persistentVolume.size='10Gi' \
--set mongodb-replicaset.persistentVolume.size='10Gi' \
--set zenko-queue.persistence.size='1Gi'
```
- Please note that these values are simply to maintain the same volume sizes from original install which is immutable in kubernetes systems after deployment. This will not "decrease" or change your volume size.
Upgrading from RC4 requires specific upgrade parameters as well see the Zenko RC5 build notes

Merges

chore: tag 1.0.0
[backbeat]: bump image to 8.0.15
[backbeat]: bump image to 8.0.14
[cloudserver]: bump image to 8.0.16
[cloudserver]: bump image tag to 8.0.15
[backbeat]: bump image tag to 8.0.13
bugfix: re enable storage location quota tests
bugfix: redis chart corner cases
[cloudserver] bugfix: redis-hosts template typo

Zenko - 1.0.0-RC7

Published by ssalaues about 6 years ago

Changelog

NOTES

MongoDB init issues have been resolved in this RC
Partitions and replicationfactor in zenko-queue (Kafka) topics can now be reconfigured/tuned post install
- Due to these changes, you may see a zenko-queue-configpod which handles the topic creation/updates
- This is created by a kubernetes job that will run until it reaches a Completed state
- In some cases, if your zenko-queue is not fully operational or not yet stabilized you may see a version of the pod in a Failed state. This is normal and the job will retry until it is successful.
- Any Failed or Completed pods can be safely deleted
Improved install documentation

Merges

bump chart versions to RC7
bump backbeat container image:
bump cloudserver container image:
Merge branch 'bugfix/ZENKO-1141-revert' into q/0.9
Revert "ZENKO-1134 [zenko-queue]: cleanup job when it succeeds"
Merge branch 'improvement/stale-bot-configuration' into q/0.9
Merge branch 'feature/ZENKO-1134-cleanup-job' into q/0.9
ZENKO-1134 [zenko-queue]: cleanup job when it succeeds
chore: add stale bot configuration
ZENKO-1131 bugfix: zenko-queue-config unmanageable spawns
ZENKO-1121 feat: reassign topic partitions
bump cloudserver container image:
bump backbeat container image:
Merge branch 'bugfix/ZENKO-1130-redis-fixes' into q/0.9
Changes to Installation_Guide.rst
bf: move security context to pod level
bf: fix readiness typo
Merge branch 'feature/ZENKO-472_Setup_Cosbench_Nightly_Run' into q/0.9
feat(ZENKO-472): Setup nightly cosbench run
cloudserver bump to 8.0.12
backbeat bump to 8.0.10
bf: fail init if quorum check fails
Fix a few remaining env vars, and remove testing branch
Merge branch 'improvement/ZENKO-1021_Restructure_end_to_end_tests' into q/0.9
Merge branch 'improvement/ZENKO-1098-update-zenko-queue-chart' into q/0.9
ci(create_buckets): add ignored pods
ZENKO-1093 bugfix: increase zenko-queue max message size
ZENKO-1088 feat: manage zenko-queue topics statically
Merge branch 'improvement/pull-request-template' into q/0.9
Merge branch 'feature/ZENKO-667/side-band-protocol-ports' into q/0.9
ZENKO-1098 feat: update zenko-queue chart to 0.9.1
Add edge build of orbit-sim and verbose logging (drop)
Add documentation
Standardize evnironment variable names and update build
Move tests and merge into one image
github: add pull request template
Merge branch 'bugfix/ZENKO-1022-flakyMetricTests' into q/0.9
Merge branch 'bugfix/ZENKO-1085-improve-backbeat-liveness-probes' into q/0.9
ft: ZENKO-667: side band protocols
bf: ZENKO-1022 Address flaky e2e metrics tests
bf: ZENKO-1092: fix redis info for NFS
bugfix: ZENKO-1024 Add pending counters tests
ZENKO-1085 bugfix: backbeat liveness probes

Zenko - 1.0.0-RC6

Published by ssalaues about 6 years ago

Changelog

NOTES

Dashboards have been added to Grafana for application level metrics/monitoring #297
New Zenko options for CRR parallelism #303
Values files with default storage, pdb, and resources requests/limits have been added #289

Known Issues:

Upgrading from 1.0.0-RC4 requires a specific upgrade procedure for close to seamless upgrades:
- helm upgrade <release-name> ./zenko --set redis-ha.enabled=false --timeout 600 && helm upgrade <release-name> ./zenko --set redis-ha.enabled=true
- This can take several minutes because helm is waiting on the removal of the old redis-ha chart. On larger deployments, it's suggested to increase the timeout to prevent early termination of the upgrade.
- This procedure is necessary because of the drastic changes in the redis-ha that fixes high availability issues along with default stateful options
Sometimes upgrades result in one MongoDB pod to be stuck during the Init:2/3 process. While functionality is still present, it's necessary to resolve this manually
- This requires to manually exec into the stuck pod and run /work-dir/peer-finder -on-start=/init/on-start.sh -service=<release-name>-mongodb-replicaset

Merges

Merge branch 'feature/ZENKO-1065-crr-parallelism' into q/0.9
Merge branch 'bugfix/ZENKO-1004/mark-one-to-many-tests-flaky' into q/0.9
ZENKO-1065 [zenko]: add crrParallelism anchor
ZENKO-1065 [backbeat]: add replicaFactor
ZENKO-1065 [zenko-queue]: add partition count and factor
bugfix: ZENKO-1004 Tag one-to-many tests as flaky
Bump versions to RC6
ZENKO-1055 bugfix: bump grafana sidecar version
ZENKO-965 bugfix: incorrect Grafana password
ZENKO-1059 refactor: cloudserver dashboard
ZENKO-511 feat: add mongodb-replicaset dashboard
ZENKO-513 feat: add backbeat dashboard
bugfix: Prometheus datasource port
Merge branch 'bugfix/ZENKO-1051_Change_to_sentinel_redis_config' into q/0.9
Bump cloudserver and backbeat images
ZENKO-1051 Add support for redis sentinels
ft: retain s3-data pvc on helm delete
ft: set default mongodb pdb for Zenko
ft: Add storage, resources, and disruption options files

Zenko - 1.0.0-RC5

Published by ssalaues about 6 years ago

Changelog

NOTES:

Folder restructure: Zenko helm chart can now be found in the kubernetes/zenko folder #278
Sub charts can be found in kubernetes/zenko/charts
- Because of the restructuring, helm dependency build is no longer a necessary part of the installation
Prometheus metrics are enabled in MongoDB #249
Prometheus has been converted to a highly available stateful set #267
- Because of these changes previous Prometheus data will not automatically transfer to the new statefulset and will be lost after upgrades
Improved HA capabilities with new redis-ha chart #264
HA support for Prometheus with StatefulSets. Default number of replicas is now 2 #267

Known Issues:

Upgrading from 1.0.0-RC4 requires a specific upgrade procedure for close to seamless upgrades:
- helm upgrade <release-name> ./zenko --set redis-ha.enabled=false --timeout 600 && helm upgrade <release-name> ./zenko --set redis-ha.enabled=true
- This can take several minutes because helm is waiting on the removal of the old redis-ha chart. On larger deployments, it's suggested to increase the timeout to prevent early termination of the upgrade.
- This procedure is necessary because of the drastic changes in the redis-ha that fixes high availability issues along with default stateful options
Sometimes upgrades result in one MongoDB pod to be stuck during the Init:2/3 process. While functionality is still present, it's necessary to resolve this manually
- This requires to manually exec into the stuck pod and run /work-dir/peer-finder -on-start=/init/on-start.sh -service=<release-name>-mongodb-replicaset