Upgrade from 1.25.0 to 1.26.0

Changes to the Cluster-UI Settings

In the Encode -> Stream section of the Cluster-UI settings, we removed the dedicated field Video ID. We replaced it with a single field for all streaming services (YouTube, Twitch) and change the label to match the selected streaming service.

Table 1 New Field Labels




Video ID


To set the Consul key that used to be genvid/encode/stream/videoid you have to change it to genvid/encode/stream/channel.

Terraform variable cidr replaced by subnet_cidr_block_size in the Terraform settings.

In the Terraform settings, we replaced the variable cidr with subnet_cidr_block_size. This change fixes a known issue causing subnet collisions when updating clusters. The subnet IPs are now set to and this variable controls the cidr size.

For example, if you set subnet_cidr_block_size to 27, the subnet IPs will start at Other subnet IPs will be distributed proportionally across all availability zones.

Terraform variables Stage and Namespace removed.

We removed the Terraform variables Stage and Namespace from all Terraform modules.

AWS and Azure tag Name renamed genvid:cluster-name.

Terraform modules now allow users to define their own custom tags. To prevent clashes between Genvid default tags and user defined tags, we updated Genvid tags with the prefix genvid:.

In AWS, this causes the column Name to be empty. As a workaround, either add a column for the tag genvid:cluster-name in the EC2 console.

From the AWS Management Console:

  1. Click EC2.

  2. Click Instances.

  3. Click the settings button (gear icon).

  4. Select the tags you want columns for.

See the AWS documentation for more information about managing tags.

In Azure, the resources are still all available under the same resource group.

This will impact existing clusters only if they are updated.

Renamed 2 metrics sent by gvencode.

We renamed 2 metrics sent by gvencode due to typos in their names.

  • compostionssent is now compositionsent.

  • compostionssentsize is now compositionsizesent.

We didn’t update the names in the SDK documentation, as they were already correct there.

AWS and Azure indexed resources are now 0-based instead of 1-based.

Previously, resources that had names or identification that contained a number were 1-based. This yielded names like server-1, game-1, etc.

Starting with the release of 1.26.0, we changed the index to be 0-based. Identifiers will now start at 0: server-0, game-0, etc.

Updating Terraform modules found in previous versions.

You may run into an error if you’re updating a bastion server created from an earlier installation of Terraform. This error occurs when reimporting the new version of the module and running plan apply.

on main.tf.json line 118, in variable:
118:     "bastionid": {

The root module input variable "bastionid" is not set, and has no default
value. Use a -var or -var-file command line argument to provide a value for
this variable.

To fix this issue:

  1. Add a global variable named bastionid.

  2. Set the value of bastionid to the name of the bastion server you’re updating.

  3. Run plan apply.