zCompute Release Notes

This document describes the Zadara Compute (zCompute) release notes. These release notes contain important information available at the time of the release. New features, important bug fixes, known limitations are addressed here.

Key Enhancements

Release 21.12 is an enhancement release to the previous Zadara 21.10 release which includes scalability, security, usability improvements, new features and bug fixes.

The following section will breakdown the additions and updates to the Zadara Compute Cloud platform (zCompute).

Support multiple subnet ranges for Elastic IPs

It is now possible to add multiple non-contiguous subnets to the same Elastic IP pool. Each may have its own gateway. This is aligned with the way site operators purchase public IP ranges. As part of the change Zadara added the following enhancement:

  • The ability to add multiple subnet ranges to the same Elastic IP pool

  • Each subnet may have its own default gateway

  • Virtual Routers will not consume Public IPs anymore, instead a single public IP will serve the entire edge network. This IP is required to access external name servers.

Current limitations:

  • Implicit DNAT Functionality is deprecated and will stop working in one of the next releases. This means: a VM without an EIP will not be able to reach an external destination. If such a flow is required, customers should use the explicit NAT GW service to implement this functionality. Also note that certain OS (e.g. Ubuntu, Windows) configuration for Zeroconf will overlap and interfere with the edge routers subnet address range - VM using DNAT cannot access VM using EIP.

  • Can’t retire a subnet from the edge network without removing all the EIP from this subnet that is in use by instances. The Edge network DNS servers that are configured for the edge network must be accessible from all edge subnets If multiple edge subnets are configured, then all of them must be configured with the same DNS servers. configuring different DNS servers for different subnets will cause unexpected behavior

  • These features require additional upgrade procedures for existing VPCs as external connectivity will be temporarily disrupted.

Site operators, for more info please contact Zadara support

CentOS 8 has been added to the zCompute Machine Images Marketplace

Following customer requests, we added a link to download CentOS 8 to our marketplace.


Customize the system TLS certificate

MSPs that have cloud administration rights can now easily update the web service TLS certificate via the API or UI, without the need to contact Zadara support.

Go to configuration -> Cluster certificates. You’ll see the default self signed certificate To upload the certificate just click the + button and upload the public certificate and private key.

Certificate - The certificate file is the end-user certificate for your domain which you received from the certificate authority. Drop the certificate file in the designated area, -or- Browse to the location.

Private Key - The private key file is the file which contains the private key which matches your certificate. Drop the private key file in the designated area, -or- Browse to the location.

Private Key Passphrase - In case the private key is encrypted by password, the passphrase should be specified in this field, otherwise the field should be omitted.

On certificate creation the cluster will validate that the certificate is not expired. After creating the certificate, it can be installed by selecting it and clicking “Install”.

Known issues: The certificate can’t be updated while there are nodes in maintenance or in failed states and therefore unreachable. There is a GUI validation to prevent certificate change in these cases.

Cluster certificate operation validates nodes are active before starting


Revision History

  • 21.12, December 2021

  • 21.10, November 2021

  • R7, V21.4.0, April 2021

  • R5, V21.1.0, January 2021

  • R4, V5.5.4, November 2020

  • R3, V5.5.3, October 2020