How to Update Open Cluster Management Add-ons in Order: dev stg prod
By combining ProgressivePerGroup with Placement decision groups, you can roll out add-on configuration changes in the order dev → stg → prod. In this article, I use cluster-proxy as an example to explain the required configuration and how the rollout actually works. Overview flowchart TB Upgrade["helm upgrade<br/>change tag to vX.Y.Z"] subgraph Hub["Hub cluster"] direction TB…
To update Open Cluster Management add-ons in the order of dev → stg → prod, you must first split ManagedCluster resources into separate environments: dev, stg, and prod. Then, define the rollout order using a Placement. Create a Placement named "cluster-proxy-placement" with predicates that select clusters with cluster-proxy: enabled and an environment label of dev, stg, or prod.
The decisionStrategy is set to groupStrategy, dividing the clusters into decision groups based on their environment. There are three decision groups: dev, stg, and prod. The rollout order is determined by the order of these decision groups.
Configure ProgressivePerGroup on the cluster-proxy ClusterManagementAddOn. Set minSuccessTime to 5 minutes, progressDeadline to 15 minutes, and maxFailures to 0. Update the add-on configuration, updating ManagedProxyConfiguration. The rollout runs from dev to stg to prod, with the Success and minSuccessTime requirements being met before proceeding to the next group.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
