Upgrade Mission Control using Helm
You can upgrade Mission Control to the latest version using Helm to take advantage of new features and improvements.
DataStax recommends that you schedule upgrades during low-activity periods, avoid scheduling new backup jobs during the upgrade window, and pause long-running repair operations before you start the upgrade.
|
Run an upgrade only on a single control plane or a data plane at any given time. You must upgrade all data plane clusters first, and then proceed to upgrade the control plane. |
In-service upgrade considerations
Different deployment architectures might exhibit different behaviors during upgrades. In-service upgrades of Mission Control affect the following components and features.
System availability
The Mission Control UI remains accessible throughout the upgrade process with no downtime. The upgrade process ensures service continuity during component updates. If enabled, Grafana dashboards remain accessible during the upgrade.
Vector continues collecting logs during the upgrade, with log collection resuming immediately after component restart. If enabled, Loki remains available for log queries during the upgrade, with the gateway service remaining accessible even if individual Loki components restart. If enabled, Mimir continues storing metrics during the upgrade with individual components restarting independently while maintaining metrics collection through component transitions. The system does not lose data during the upgrade process.
Background operations
If enabled, backup and repair operations can be temporarily affected during the upgrade. The system tracks progress and automatically retries operations when possible. Existing backups remain intact and accessible throughout the upgrade process.
Cluster operations
You must upgrade all data plane clusters first, and then proceed to upgrade the control plane. Upgrading one datacenter doesn’t affect other datacenters, and data replication continues normally between datacenters during upgrades. Inter-datacenter communication remains functional.
Database clusters continue running normally during the Mission Control upgrade. The system might temporarily make cluster management operations unavailable during the upgrade, while monitoring and health checks continue throughout the process.
Performance considerations
The upgrade process might temporarily increase resource usage on management nodes, including CPU and memory consumption, additional network traffic during component updates, and temporary increases in disk I/O during component restarts and updates.
Use Helm to upgrade Mission Control
Run the following command to upgrade Mission Control:
helm upgrade mission-control oci://registry.replicated.com/mission-control/mission-control --namespace mission-control --create-namespace -f values.yaml