Applying version-specific hotfixes

Use these procedures to apply version-specific hotfixes to Hedge core and Docker-Compose-based Hedge nodes. By targeting specific services and leveraging version tags, you can address critical issues without disrupting the entire system. The procedure also provides steps to roll back a specific service to its previous version in case of bugs, performance issues, or unexpected behavior.  

To apply a version-specific hotfix to core

1. Navigate to the <hedge-core-installer>/ansible/hedge_services.yaml file.
2. Determine the target services that require the hotfix, for example, hedge-admin and hedge-init.
3. Modify image_tag_override by locating the corresponding service_name section for each targeted service.
4. Update the image_tag_override value to the latest hotfix, for example, enter 24.x.y.123_GA.

5. Apply the updated configuration to your Kubernetes cluster by using the appropriate deployment mechanism.

   Note

   To use the default version for a service, leave the image_tag_override field empty.

6. Run the following command to redeploy a specific service after changing the tags:

   Bash
   > ./deploy.sh <namespace-name> service <service-name>

To roll back a specific service in the Hedge core to its previous version

You can perform the rollback procedure to revert a specific service in the Hedge Core system to its last version. 

1. Navigate to the <hedge-core-installer>/ansible directory.
2. Open the hedge_services.yaml file.
3. Locate the section in the YAML file corresponding to the service you want to roll back.
4. In the target service's section, locate the image_tag_override line.
5. Remove the value of image_tag_override.
6. Save the modified hedge_services.yaml file.
7. Navigate to the <hedge-core-installer> directory.

8. Run the following command by replacing placeholders with actual values:

   Bash
   ./deploy.sh <namespace-name> -service <service-name>

To apply a version-specific hotfix to Docker Compose-based nodes

1. Navigate to the <hedge-node-installer>/.env file.
2. Determine the services that require the hotfix, for example, hedge-admin and hedge-init.
3. Modify the _TAG variables by finding the corresponding _TAG variable for each targeted service, for example, locate HEDGE_ADMIN_DOCKER_TAG and HEDGE_INIT_DOCKER_TAG.
4. Update the tag value by replacing the existing one with the latest hotfix, for example, enter 24.x.y.123_GA.

5. Run the following command to trigger the installation with the updated tags:

   Bash
   make run env=node hedge-admin hedge-init 

   Note

   To use the default version for a service, leave the corresponding _TAG field for that service empty. 

To roll back a specific service in the Hedge node to its previous version

You can perform the rollback service within the Hedge-Node environment to its last version. 

1. Navigate to the <hedge-node-installer> directory
2. Open the .env file.
3. Locate the line in the .env file that defines the _TAG for the service you want to roll back.
4. Delete the existing value assigned to the _TAG variable.
5. Save the modified .env file.
6. Navigate to the <hedge-node-installer> directory.

7. Run the following command:
   

   Bash
   make run env=node hedge-admin hedge-init