GritivaCore Upgrade Guide#

This document provides a comprehensive guide for upgrading the GritivaCore agent on your virtual machines (VMs). It is critical to follow the outlined steps to ensure a smooth upgrade process while maintaining compatibility with the hosted control plane.

Before proceeding with the upgrade, ensure that you have the following:

• Current version of the GritivaCore agent installed. Check using:

  gritivactl version

• Available version for upgrade. Check using:

  gritivactl version --remote

• Compatibility with the control plane (agents must be within 2 minor versions of the control plane).

The upgrade process consists of the following steps:

Step 1: Backup#

Ensure that you have backups of your current configuration and data.

Step 2: Upgrade Process#

To upgrade a single agent, run the following command:

curl -fsSL https://get.gritiva.com/agent | sudo bash -s -- --upgrade

For a rolling upgrade across a fleet, use:

gritivactl agent rolling-upgrade --batch 1 --observe 24h

Step 3: Post-Upgrade Checks#

After the upgrade, verify the status of the agent using:

gritivactl status

Ensure that it shows healthy mesh peers and no panicked scopes.

If you encounter issues after the upgrade, you can roll back to a previous version using the following command:

curl -fsSL https://get.gritiva.com/agent | sudo bash -s -- --pin-version 2.4.0

Replace 2.4.0 with the version you wish to revert to.

If you experience issues during the upgrade process, refer to the CHANGELOG.md for any breaking changes and ensure that your agent is compatible with the control plane.

Q: What should I do if the upgrade fails?#

A: Check the logs for errors and ensure that your agent is within the compatibility window.

Q: How can I verify the upgrade was successful?#

A: Use the command gritivactl status to confirm that all peers are healthy.