Topology Aware Lifecycle Manager
TALM manages how changes like cluster upgrades, Operator upgrades, and cluster configuration are rolled out to the network.
- New in this release
-
-
No reference design updates in this release
-
- Description
-
TALM is an Operator that runs only on the hub cluster for managing how changes like cluster upgrades, Operator upgrades, and cluster configuration are rolled out to the network. TALM supports the following features:
-
Progressive rollout of policy updates to fleets of clusters in user configurable batches.
-
Per-cluster actions add
ztp-donelabels or other user-configurable labels following configuration changes to managed clusters. -
Precaching of single-node OpenShift clusters images: TALM supports optional pre-caching of OpenShift, OLM Operator, and additional user images to single-node OpenShift clusters before initiating an upgrade. The precaching feature is not applicable when using the recommended image-based upgrade method for upgrading single-node OpenShift clusters.
-
Specifying optional pre-caching configurations with
PreCachingConfigCRs. Review the sample referencePreCachingConfigCR for more information. -
Excluding unused images with configurable filtering.
-
Enabling before and after pre-caching storage space validations with configurable space-required parameters.
-
-
- Limits and requirements
-
-
Supports concurrent cluster deployment in batches of 400
-
Pre-caching and backup are limited to single-node OpenShift clusters only
-
- Engineering considerations
-
-
The
PreCachingConfigCR is optional and does not need to be created if you only need to precache platform-related OpenShift and OLM Operator images. -
The
PreCachingConfigCR must be applied before referencing it in theClusterGroupUpgradeCR. -
Only policies with the
ran.openshift.io/ztp-deploy-waveannotation are automatically applied by TALM during cluster installation. -
Any policy can be remediated by TALM under control of a user created
ClusterGroupUpgradeCR.
-