Full IDEA Upgrade (idea-admin.sh upgrade-cluster)
Full Cluster Upgrade
Overview
The upgrade-cluster
command combines multiple steps that were previously separate into a single operation:
Updating the base OS configuration
Updating infrastructure AMIs
Backing up and regenerating global settings
Deploying all modules with the
--upgrade
flag
Usage
The basic syntax for the upgrade command is:
If no modules are specified, all modules will be upgraded automatically.
Required Parameters
--cluster-name
: Name of your IDEA cluster--aws-region
: AWS region where the cluster is deployed
Optional Parameters
MODULES
: List of modules to upgrade (e.g.,cluster
,metrics
,scheduler
, etc.). If not specified, all modules will be upgraded.--base-os
: New base OS to upgrade to. If not specified, defaults toamazonlinux2023
. Supported options are:amazonlinux2023
(default)rhel8
rhel9
rocky8
rocky9
--aws-profile
: AWS profile to use for the operation--termination-protection
: Set CloudFormation stack termination protection (default: true)--force-build-bootstrap
: Re-build bootstrap package even if directory exists--rollback/--no-rollback
: Enable/disable stack rollback on failure (default: true)--optimize-deployment
: Deploy applicable stacks in parallel to speed up the process--force
: Skip all confirmation prompts--skip-global-settings-update
: Skip the global settings update if you've already done it--module-set
: Name of the module set to use (default: default)--deployment-id
: UUID to identify the deployment
Examples
Full Upgrade to Default Base OS (Amazon Linux 2023)
The simplest way to upgrade all infrastructure components:
Full Upgrade with Explicit Base OS
Explicitly specify the base OS (same as default):
Upgrade Only Specific Modules
To upgrade only the scheduler and cluster-manager components:
Skip Global Settings Update
If you've already updated global settings and want to skip that step:
Optimize for Speed (experimental)
Use parallel deployment where possible:
Troubleshooting
If the upgrade fails during the pre-upgrade configuration stage:
Make sure your values.yml file correctly reflects your desired configuration
Verify AMI IDs are available in your target region
If the upgrade fails during deployment:
Check the CloudFormation console for error details
Fix any issues and retry with the same command
Use
--no-rollback
to prevent stack rollback for easier debugging
Last updated