How to Roll Out OCM Add-on Updates Sequentially Across Dev, Staging, and Prod
Open Cluster Management (OCM) supports staged add-on configuration rollouts using ProgressivePerGroup combined with Placement decision groups. By labeling ManagedCluster resources with environment tags (dev, stg, prod), administrators can define ordered decision groups within a Placement resource. The rollout progresses from dev to stg to prod, advancing to the next group only after the current group's clusters report a successful status and satisfy a minimum success time threshold. The cluster-proxy add-on serves as the example, where changes to the proxy agent image trigger a config hash update that drives the staged rollout via the OCM add-on manager. This approach ensures that hub-side updates to proxy server components happen immediately, while agent-side changes are safely propagated in a controlled, environment-by-environment sequence.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in