Skip to content

Commit 9eb6fab

Browse files
Wei WengWei Weng
Wei Weng
authored and
Wei Weng
committed
simplify and add examples
Signed-off-by: Wei Weng <[email protected]>
1 parent 3d290b2 commit 9eb6fab

8 files changed

Lines changed: 210 additions & 37 deletions

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementapplied-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,44 @@
11
---
2-
title: ClusterResourcePlacementApplied / ResourcePlacementApplied failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: PlacementApplied failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve ClusterResourcePlacementApplied or ResourcePlacementApplied failure when you propagate resources by using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager APIs.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
99

10-
# Resource propagation failure: ClusterResourcePlacementApplied / ResourcePlacementApplied is False
10+
# Resource propagation failure: PlacementApplied is False
1111

12-
This article discusses how to troubleshoot `ClusterResourcePlacementApplied` (for ClusterResourcePlacement) or `ResourcePlacementApplied` (for ResourcePlacement) issues when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager.
12+
This article discusses how to troubleshoot resource application failures when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
13+
14+
- `ClusterResourcePlacementApplied` for ClusterResourcePlacement
15+
- `ResourcePlacementApplied` for ResourcePlacement
16+
17+
Sample error messages:
18+
19+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
20+
21+
```yaml
22+
- lastTransitionTime: "2024-05-07T23:32:40Z"
23+
message: Failed to apply resources to 1 clusters, please check the `failedPlacements` status
24+
observedGeneration: 1
25+
reason: ApplyFailed
26+
status: "False"
27+
type: ClusterResourcePlacementApplied
28+
```
29+
30+
# [ResourcePlacement](#tab/resourceplacement)
31+
32+
```yaml
33+
- lastTransitionTime: "2024-05-07T23:32:40Z"
34+
message: Failed to apply resources to 1 clusters, please check the `failedPlacements` status
35+
observedGeneration: 1
36+
reason: ApplyFailed
37+
status: "False"
38+
type: ResourcePlacementApplied
39+
```
40+
41+
---
1342
1443
## Symptoms
1544

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementavailable-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,44 @@
11
---
2-
title: ClusterResourcePlacementAvailable / ResourcePlacementAvailable failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: PlacementAvailable failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve ClusterResourcePlacementAvailable or ResourcePlacementAvailable failure when you propagate resources by using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager APIs.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
99

10-
# Resource propagation failure: ClusterResourcePlacementAvailable / ResourcePlacementAvailable is False
10+
# Resource propagation failure: PlacementAvailable is False
1111

12-
This article discusses how to troubleshoot `ClusterResourcePlacementAvailable` (for ClusterResourcePlacement) or `ResourcePlacementAvailable` (for ResourcePlacement) issues when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager.
12+
This article discusses how to troubleshoot resource availability failures when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
13+
14+
- `ClusterResourcePlacementAvailable` for ClusterResourcePlacement
15+
- `ResourcePlacementAvailable` for ResourcePlacement
16+
17+
Sample error messages:
18+
19+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
20+
21+
```yaml
22+
- lastTransitionTime: "2024-05-07T23:32:40Z"
23+
message: Failed to check the availability of resources in 1 clusters, please check the `failedPlacements` status
24+
observedGeneration: 1
25+
reason: ResourcesUnavailable
26+
status: "False"
27+
type: ClusterResourcePlacementAvailable
28+
```
29+
30+
# [ResourcePlacement](#tab/resourceplacement)
31+
32+
```yaml
33+
- lastTransitionTime: "2024-05-07T23:32:40Z"
34+
message: Failed to check the availability of resources in 1 clusters, please check the `failedPlacements` status
35+
observedGeneration: 1
36+
reason: ResourcesUnavailable
37+
status: "False"
38+
type: ResourcePlacementAvailable
39+
```
40+
41+
---
1342
1443
## Symptoms
1544

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementoverridden-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,44 @@
11
---
2-
title: ClusterResourcePlacementOverridden / ResourcePlacementOverridden failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: PlacementOverridden failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve ClusterResourcePlacementOverridden or ResourcePlacementOverridden failure when you propagate resources by using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager APIs.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
99

10-
# Resource propagation failure: ClusterResourcePlacementOverridden / ResourcePlacementOverridden is False
10+
# Resource propagation failure: PlacementOverridden is False
1111

12-
This article discusses how to troubleshoot `ClusterResourcePlacementOverridden` (for ClusterResourcePlacement) or `ResourcePlacementOverridden` (for ResourcePlacement) issues when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager.
12+
This article discusses how to troubleshoot override failures when you propagate resources by using placement APIs in Microsoft Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
13+
14+
- `ClusterResourcePlacementOverridden` for ClusterResourcePlacement
15+
- `ResourcePlacementOverridden` for ResourcePlacement
16+
17+
Sample error messages:
18+
19+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
20+
21+
```yaml
22+
- lastTransitionTime: "2024-05-07T23:32:40Z"
23+
message: Failed to override resources for 1 clusters, please check the `failedPlacements` status
24+
observedGeneration: 1
25+
reason: OverrideFailed
26+
status: "False"
27+
type: ClusterResourcePlacementOverridden
28+
```
29+
30+
# [ResourcePlacement](#tab/resourceplacement)
31+
32+
```yaml
33+
- lastTransitionTime: "2024-05-07T23:32:40Z"
34+
message: Failed to override resources for 1 clusters, please check the `failedPlacements` status
35+
observedGeneration: 1
36+
reason: OverrideFailed
37+
status: "False"
38+
type: ResourcePlacementOverridden
39+
```
40+
41+
---
1342
1443
## Symptoms
1544

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementrolloutstarted-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,43 @@
11
---
2-
title: ClusterResourcePlacementRolloutStarted / ResourcePlacementRolloutStarted failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: PlacementRolloutStarted failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve the ClusterResourcePlacementRolloutStarted or ResourcePlacementRolloutStarted failure when you propagate resources using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai, v-weizhu
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
9-
# Resource propagation failure: ClusterResourcePlacementRolloutStarted / ResourcePlacementRolloutStarted is false
9+
# Resource propagation failure: PlacementRolloutStarted is false
1010

11-
This article describes how to troubleshoot `ClusterResourcePlacementRolloutStarted` (for ClusterResourcePlacement) or `ResourcePlacementRolloutStarted` (for ResourcePlacement) issues when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager.
11+
This article describes how to troubleshoot rollout initiation failures when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
12+
13+
- `ClusterResourcePlacementRolloutStarted` for ClusterResourcePlacement
14+
- `ResourcePlacementRolloutStarted` for ResourcePlacement
15+
16+
Sample error messages:
17+
18+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
19+
20+
```yaml
21+
- lastTransitionTime: "2024-05-07T23:32:40Z"
22+
message: The rollout is being blocked by the rollout strategy
23+
observedGeneration: 1
24+
reason: RolloutNotStartedYet
25+
status: "False"
26+
type: ClusterResourcePlacementRolloutStarted
27+
```
28+
29+
# [ResourcePlacement](#tab/resourceplacement)
30+
31+
```yaml
32+
- lastTransitionTime: "2024-05-07T23:32:40Z"
33+
message: The rollout is being blocked by the rollout strategy
34+
observedGeneration: 1
35+
reason: RolloutNotStartedYet
36+
status: "False"
37+
type: ResourcePlacementRolloutStarted
38+
```
39+
40+
---
1241
1342
## Symptoms
1443

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementscheduled-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,43 @@
11
---
2-
title: ClusterResourcePlacementScheduled / ResourcePlacementScheduled failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: PlacementScheduled failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve the ClusterResourcePlacementScheduled or ResourcePlacementScheduled failure when you propagate resources using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai, v-weizhu
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
9-
# Resource propagation failure: ClusterResourcePlacementScheduled / ResourcePlacementScheduled is false
9+
# Resource propagation failure: PlacementScheduled is false
1010

11-
This article describes how to troubleshoot `ClusterResourcePlacementScheduled` (for ClusterResourcePlacement) or `ResourcePlacementScheduled` (for ResourcePlacement) issues when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager.
11+
This article describes how to troubleshoot scheduling failures when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
12+
13+
- `ClusterResourcePlacementScheduled` for ClusterResourcePlacement
14+
- `ResourcePlacementScheduled` for ResourcePlacement
15+
16+
Sample error messages:
17+
18+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
19+
20+
```yaml
21+
- lastTransitionTime: "2024-05-07T23:32:40Z"
22+
message: "couldn't find all the clusters needed as specified by the scheduling policy"
23+
observedGeneration: 1
24+
reason: SchedulingPolicyUnfulfilled
25+
status: "False"
26+
type: ClusterResourcePlacementScheduled
27+
```
28+
29+
# [ResourcePlacement](#tab/resourceplacement)
30+
31+
```yaml
32+
- lastTransitionTime: "2024-05-07T23:32:40Z"
33+
message: "couldn't find all the clusters needed as specified by the scheduling policy"
34+
observedGeneration: 1
35+
reason: SchedulingPolicyUnfulfilled
36+
status: "False"
37+
type: ResourcePlacementScheduled
38+
```
39+
40+
---
1241
1342
## Symptoms
1443

‎support/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementworksynchronized-false.md‎

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,43 @@
11
---
2-
title: ClusterResourcePlacementWorkSynchronized / ResourcePlacementWorkSynchronized failure when using placement APIs in Azure Kubernetes Fleet Manager
2+
title: WorkSynchronized failure when using placement APIs in Azure Kubernetes Fleet Manager
33
description: Helps you resolve the ClusterResourcePlacementWorkSynchronized or ResourcePlacementWorkSynchronized failure when you propagate resources using the ClusterResourcePlacement or ResourcePlacement API object in Azure Kubernetes Fleet Manager.
44
ms.date: 12/09/2025
55
ms.reviewer: zhangryan, chiragpa, shasb, ericlucier, arfallas, sachidesai, v-weizhu
66
ms.service: azure-kubernetes-fleet-manager
77
ms.custom: sap:Other issue or questions related to Fleet manager
88
---
9-
# Resource propagation failure: ClusterResourcePlacementWorkSynchronized / ResourcePlacementWorkSynchronized is false
9+
# Resource propagation failure: WorkSynchronized is false
1010

11-
This article describes how to troubleshoot `ClusterResourcePlacementWorkSynchronized` (for ClusterResourcePlacement) or `ResourcePlacementWorkSynchronized` (for ResourcePlacement) issues when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager.
11+
This article describes how to troubleshoot work synchronization failures when you propagate resources using placement APIs in Azure Kubernetes Fleet Manager. This issue applies to both `ClusterResourcePlacement` and `ResourcePlacement`, each with their own dedicated custom resource condition types:
12+
13+
- `ClusterResourcePlacementWorkSynchronized` for ClusterResourcePlacement
14+
- `ResourcePlacementWorkSynchronized` for ResourcePlacement
15+
16+
Sample error messages:
17+
18+
# [ClusterResourcePlacement](#tab/clusterresourceplacement)
19+
20+
```yaml
21+
- lastTransitionTime: "2024-05-07T23:32:40Z"
22+
message: Failed to synchronize work(s) for 1 clusters, please check the `failedPlacements` status
23+
observedGeneration: 1
24+
reason: WorkNeedSyncedOrUpdated
25+
status: "False"
26+
type: ClusterResourcePlacementWorkSynchronized
27+
```
28+
29+
# [ResourcePlacement](#tab/resourceplacement)
30+
31+
```yaml
32+
- lastTransitionTime: "2024-05-07T23:32:40Z"
33+
message: Failed to synchronize work(s) for 1 clusters, please check the `failedPlacements` status
34+
observedGeneration: 1
35+
reason: WorkNeedSyncedOrUpdated
36+
status: "False"
37+
type: ResourcePlacementWorkSynchronized
38+
```
39+
40+
---
1241
1342
## Symptoms
1443

‎support/azure/kubernetes-fleet/cluster-resource-placement/troubleshoot-resource-placement-issues.md‎

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,18 @@ This troubleshooting guide helps you resolve `ResourcePlacement` API object-rela
1919

2020
For more information about each object, see the [KubeFleet API reference](https://kubefleet-dev.github.io/website/docs/api-reference/).
2121

22+
## Relationship between ResourcePlacement and ClusterResourcePlacement
23+
24+
ResourcePlacement and ClusterResourcePlacement share the same underlying architecture with a one-to-one mapping of condition types. The troubleshooting approaches documented in the ClusterResourcePlacement troubleshooting guides are applicable to ResourcePlacement as well. The main difference is that ResourcePlacement is namespace-scoped and works with namespace-scoped resources, while ClusterResourcePlacement is cluster-scoped.
25+
26+
The condition types follow a naming convention where ResourcePlacement conditions use the `ResourcePlacement` prefix while ClusterResourcePlacement conditions use the `ClusterResourcePlacement` prefix. For example:
27+
28+
- `ResourcePlacementScheduled` ↔ `ClusterResourcePlacementScheduled`
29+
- `ResourcePlacementApplied` ↔ `ClusterResourcePlacementApplied`
30+
- `ResourcePlacementAvailable` ↔ `ClusterResourcePlacementAvailable`
31+
32+
When following ClusterResourcePlacement troubleshooting guidance, substitute the appropriate ResourcePlacement condition names and commands (for example, use `kubectl get resourceplacement -n <namespace>` instead of `kubectl get clusterresourceplacement`).
33+
2234
## Important considerations for ResourcePlacement
2335

2436
### Namespace prerequisites
@@ -49,19 +61,6 @@ ResourcePlacement can only select and manage namespace-scoped resources within t
4961
- ❌ **Not Supported**: Cluster-scoped resources (use ClusterResourcePlacement instead)
5062
- ❌ **Not Supported**: Resources in other namespaces
5163

52-
## Relationship between ResourcePlacement and ClusterResourcePlacement
53-
54-
> [!NOTE]
55-
> ResourcePlacement and ClusterResourcePlacement share the same underlying architecture with a one-to-one mapping of condition types. The troubleshooting approaches documented in the ClusterResourcePlacement troubleshooting guides are applicable to ResourcePlacement as well. The main difference is that ResourcePlacement is namespace-scoped and works with namespace-scoped resources, while ClusterResourcePlacement is cluster-scoped.
56-
>
57-
> The condition types follow a naming convention where ResourcePlacement conditions use the `ResourcePlacement` prefix while ClusterResourcePlacement conditions use the `ClusterResourcePlacement` prefix. For example:
58-
>
59-
> - `ResourcePlacementScheduled` ↔ `ClusterResourcePlacementScheduled`
60-
> - `ResourcePlacementApplied` ↔ `ClusterResourcePlacementApplied`
61-
> - `ResourcePlacementAvailable` ↔ `ClusterResourcePlacementAvailable`
62-
>
63-
> When following ClusterResourcePlacement troubleshooting guidance, substitute the appropriate ResourcePlacement condition names and commands (for example, use `kubectl get resourceplacement -n <namespace>` instead of `kubectl get clusterresourceplacement`).
64-
6564
## Complete progression of the ResourcePlacement deployment
6665

6766
Understanding the progression and status of the `ResourcePlacement` custom resource is crucial for diagnosing and identifying failures. You can view the status of the `ResourcePlacement` custom resource by using the following command:

‎support/azure/kubernetes-fleet/toc.yml‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,17 +7,17 @@
77
href: cluster-resource-placement/troubleshoot-clusterresourceplacement-api-issues.md
88
- name: Troubleshooting Resource Placement
99
href: cluster-resource-placement/troubleshoot-resource-placement-issues.md
10-
- name: Scheduled condition is false
10+
- name: PlacementScheduled is false
1111
href: cluster-resource-placement/crp-clusterresourceplacementscheduled-false.md
12-
- name: RolloutStarted condition is false
12+
- name: PlacementRolloutStarted is false
1313
href: cluster-resource-placement/crp-clusterresourceplacementrolloutstarted-false.md
14-
- name: Overridden condition is false
14+
- name: PlacementOverridden is false
1515
href: cluster-resource-placement/crp-clusterresourceplacementoverridden-false.md
16-
- name: WorkSynchronized condition is false
16+
- name: WorkSynchronized is false
1717
href: cluster-resource-placement/crp-clusterresourceplacementworksynchronized-false.md
18-
- name: Applied condition is false
18+
- name: PlacementApplied is false
1919
href: cluster-resource-placement/crp-clusterresourceplacementapplied-false.md
20-
- name: Available condition is false
20+
- name: PlacementAvailable is false
2121
href: cluster-resource-placement/crp-clusterresourceplacementavailable-false.md
2222

2323
- name: Multi-cluster networking

0 commit comments

Comments
 (0)