Administrator What's New > Upgrade > Preparing for the upgrade
  

Preparing for the upgrade

Perform the following tasks to prepare for upgrade to the latest release.

Advanced clusters on AWS

The April 2026 release upgrades advanced clusters to use Kubernetes 1.34. If you usean advanced cluster on AWS and use custom master and worker roles, update the IAM policies.
For the master role, update minimal_master_policy to the following policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:DescribeRegions",
"ec2:DescribeRouteTables",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSubnets",
"ec2:DescribeVolumes",
"ec2:DescribeAvailabilityZones", // April 2026 release requirement
"ec2:DescribeSnapshots", // April 2026 release requirement
"ec2:DescribeTags" // April 2026 release requirement
],
"Resource": [""]
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeVpcs",
"ec2:CreateTags",
"ec2:CreateVolume",
"ec2:DescribeVolumesModifications",
"ec2:ModifyInstanceAttribute",
"ec2:ModifyVolume"
],
"Resource": [""]
},
{
"Effect": "Allow",
"Action": [
"ec2:AttachVolume", // If enabling CLAIRE, move AttachVolume to the same section as CreateVolume.
"ec2:DeleteVolume",
"ec2:DetachVolume"
],
"Resource": [""],
"Condition": {
"StringLike": {
"ec2:ResourceTag/KubernetesCluster": ".k8s.local"
}
}
},
{
"Effect": "Allow",
"Action": [
"ec2:CreateSnapshot", // April 2026 release requirement
"ec2:DeleteSnapshot" // April 2026 release requirement
],
"Resource": [""]
},
{
"Effect": "Allow",
"Action": [
"autoscaling:DescribeAutoScalingGroups",
"autoscaling:DescribeLaunchConfigurations",
"autoscaling:DescribeAutoScalingInstances",
"autoscaling:DescribeTags",
"autoscaling:DescribeScalingActivities"
],
"Resource": [""]
},
{
"Effect": "Allow",
"Action": [
"autoscaling:SetDesiredCapacity",
"autoscaling:TerminateInstanceInAutoScalingGroup",
"autoscaling:UpdateAutoScalingGroup"
],
"Resource": [""],
"Condition": {
"StringLike": {
"autoscaling:ResourceTag/KubernetesCluster": ".k8s.local"
}
}
},
{
"Effect": "Allow",
"Action": [
"elasticloadbalancing:AddTags",
"elasticloadbalancing:AttachLoadBalancerToSubnets",
"elasticloadbalancing:ApplySecurityGroupsToLoadBalancer",
"elasticloadbalancing:ConfigureHealthCheck",
"elasticloadbalancing:DeleteLoadBalancer",
"elasticloadbalancing:DeleteLoadBalancerListeners",
"elasticloadbalancing:DescribeLoadBalancers",
"elasticloadbalancing:DescribeLoadBalancerAttributes",
"elasticloadbalancing:DetachLoadBalancerFromSubnets",
"elasticloadbalancing:DeregisterInstancesFromLoadBalancer",
"elasticloadbalancing:ModifyLoadBalancerAttributes",
"elasticloadbalancing:RegisterInstancesWithLoadBalancer",
"elasticloadbalancing:SetLoadBalancerPoliciesForBackendServer"
],
"Resource": [""],
"Condition": {
"StringLike": {
"elasticloadbalancing:ResourceTag/KubernetesCluster": ".k8s.local"
}
}
},
{
"Effect": "Allow",
"Action": [
"elasticloadbalancing:AddTags",
"elasticloadbalancing:DeleteListener",
"elasticloadbalancing:DeleteTargetGroup",
"elasticloadbalancing:DeregisterTargets",
"elasticloadbalancing:DescribeListeners",
"elasticloadbalancing:DescribeLoadBalancerPolicies",
"elasticloadbalancing:DescribeTargetGroups",
"elasticloadbalancing:DescribeTargetHealth",
"elasticloadbalancing:ModifyListener",
"elasticloadbalancing:ModifyTargetGroup",
"elasticloadbalancing:RegisterTargets",
"elasticloadbalancing:SetLoadBalancerPoliciesOfListener"
],
"Resource": [""],
"Condition": {
"StringLike": {
"elasticloadbalancing:ResourceTag/KubernetesCluster": ".k8s.local"
}
}
},
{
"Effect": "Allow",
"Action": [
"iam:ListServerCertificates",
"iam:GetServerCertificate"
],
"Resource": [""]
},
{
"Effect": "Allow",
"Action": [
"s3:Get*"
],
"Resource": [
"arn:aws:s3:::<cluster-staging-dir1>/"
]
},
{
"Effect": "Allow",
"Action": [
"kms:Encrypt",
"kms:Decrypt",
"kms:ReEncrypt",
"kms:GenerateDataKey*",
"kms:DescribeKey"
],
"Resource": ["*"]
}
]
}
For the worker role, update minimal_worker_policy to the following policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:DescribeRegions",
"ec2:CreateVolume", // April 2026 release requirement
"ec2:AttachVolume", // April 2026 release requirement
"ec2:DeleteVolume", // April 2026 release requirement
"ec2:DetachVolume", // April 2026 release requirement
"ec2:ModifyVolume", // April 2026 release requirement
"ec2:DescribeAvailabilityZones", // April 2026 release requirement
"ec2:DescribeSnapshots", // April 2026 release requirement
"ec2:DescribeTags", // April 2026 release requirement
"ec2:DescribeVolumes", // April 2026 release requirement
"ec2:DescribeVolumesModifications", // April 2026 release requirement
"ec2:CreateSnapshot", // April 2026 release requirement
"ec2:DeleteSnapshot" // April 2026 release requirement
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"ec2:CreateTags"
],
"Resource": [
"arn:aws:ec2:*:*:volume/*"
]
},
{
"Effect": "Allow",
"Action": [
"autoscaling:DescribeAutoScalingInstances",
"autoscaling:DescribeTags"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"s3:Get*"
],
"Resource": [
"arn:aws:s3:::<cluster-staging-dir1>/*"
]
},
{
"Effect": "Allow",
"Action": [
"kms:Encrypt",
"kms:Decrypt",
"kms:ReEncrypt*",
"kms:GenerateDataKey*",
"kms:DescribeKey"
],
"Resource": [
"*"
]
}
]
}

Disk space requirements and file preparation

The Secure Agent upgrades the first time that you access the system after the upgrade.
Files that you added to the following directory are preserved after the upgrade:
<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm-extra
Note: After a major release upgrade, the old and new versions of the services might continue to run concurrently for up to 24 hours. Ensure that the Secure Agent machine has sufficient free memory to avoid memory depletion during this period.
Perform the following steps to ensure that the Secure Agent is ready for the upgrade:
  1. 1Ensure that each Secure Agent machine has sufficient disk space and memory available for upgrade.
    2. The machine must have sufficient available memory to run two Secure Agents simulatenously.
    The machine must have at least 5 GB free space or the amount of disk space calculated using the following formula, whichever is greater:
    Minimum required free space = 3 * (size of current Secure Agent installation directory - space used for logs directory)
  2. 2Close all applications and open files to avoid file lock issues, for example: