From 0cd3e6415d5b38baabf5670d94e969b325772047 Mon Sep 17 00:00:00 2001 From: Fitsum Taye <43303103+fitsegreat@users.noreply.github.com> Date: Wed, 4 Jun 2025 21:04:44 +0300 Subject: [PATCH 1/2] Updated broken link to placement page --- .../docs/concepts/work-distribution/manifestworkreplicaset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md b/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md index bcd80be4..9199a7b1 100644 --- a/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md +++ b/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md @@ -92,7 +92,7 @@ spec: - date; echo Hello from the Kubernetes cluster ``` The **PlacementRefs** uses the Rollout Strategy [API](https://github.com/open-cluster-management-io/api/blob/main/cluster/v1alpha1/types_rolloutstrategy.go) to apply the manifestWork to the selected clusters. -In the example above; the placementRefs refers to three placements; placement-rollout-all, placement-rollout-progressive and placement-rollout-progressive-per-group. For more info regards the rollout strategies check the Rollout Strategy section at the [placement](https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/blob/main/content/en/concepts/placement.md) document. +In the example above; the placementRefs refers to three placements; placement-rollout-all, placement-rollout-progressive and placement-rollout-progressive-per-group. For more info regards the rollout strategies check the Rollout Strategy section at the [placement](https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/blob/main/content/en/docs/concepts/content-placement/placement.md) document. **Note:** The placement reference must be in the same namespace as the manifestWorkReplicaSet. ## Status tracking From 946d94cbb337c774e850ed59275ec8c1bbcda81c Mon Sep 17 00:00:00 2001 From: Fitsum Taye <43303103+fitsegreat@users.noreply.github.com> Date: Wed, 4 Jun 2025 21:15:20 +0300 Subject: [PATCH 2/2] Update content/en/docs/concepts/work-distribution/manifestworkreplicaset.md Co-authored-by: Mike Ng --- .../docs/concepts/work-distribution/manifestworkreplicaset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md b/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md index 9199a7b1..3e30b0d8 100644 --- a/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md +++ b/content/en/docs/concepts/work-distribution/manifestworkreplicaset.md @@ -92,7 +92,7 @@ spec: - date; echo Hello from the Kubernetes cluster ``` The **PlacementRefs** uses the Rollout Strategy [API](https://github.com/open-cluster-management-io/api/blob/main/cluster/v1alpha1/types_rolloutstrategy.go) to apply the manifestWork to the selected clusters. -In the example above; the placementRefs refers to three placements; placement-rollout-all, placement-rollout-progressive and placement-rollout-progressive-per-group. For more info regards the rollout strategies check the Rollout Strategy section at the [placement](https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/blob/main/content/en/docs/concepts/content-placement/placement.md) document. +In the example above; the placementRefs refers to three placements; placement-rollout-all, placement-rollout-progressive and placement-rollout-progressive-per-group. For more info regards the rollout strategies check the Rollout Strategy section at the [placement](https://open-cluster-management.io/docs/concepts/content-placement/placement/) document. **Note:** The placement reference must be in the same namespace as the manifestWorkReplicaSet. ## Status tracking