1.0.0

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