Updates

Author: ryanberg-aquent

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

@@ -9,6 +9,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 
 # Resource propagation failure: PlacementApplied is False
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementApplied` for ClusterResourcePlacement
@@ -294,14 +296,16 @@ Check the `Work` status, particularly the `manifestConditions` section. You can
 
 In the situation, set the `AllowCoOwnership` to `true` in the ApplyStrategy policy. However, the user must make the decision because the resources might not be shared.
 
-## General Troubleshooting Notes
+## General troubleshooting notes
 
 The troubleshooting process and Work object inspection are identical for both placement types:
+
 - Both use the same underlying Work API to apply resources to member clusters.
 - The Work object status and manifestConditions have the same structure regardless of the placement type that created them.
 - The main difference is the scope: the cluster-scoped placement can select both cluster-scoped and namespace-scoped resources, while the namespace-scoped placement can only select namespace-scoped resources within its own namespace.
 
 For ResourcePlacement-specific considerations:
+
 - Ensure the target namespace exists on member clusters before the ResourcePlacement tries to apply resources to it
 - ResourcePlacement can only select resources within the same namespace where the ResourcePlacement object itself resides
 

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

@@ -9,6 +9,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 
 # Resource propagation failure: PlacementAvailable is False
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementAvailable` for ClusterResourcePlacement
@@ -255,14 +257,12 @@ In the situation, check the deployment in the member cluster because the message
 
 For all other situations, make sure that the propagated resource is configured correctly. Additionally, verify that the selected cluster has sufficient available capacity to accommodate the new resources.
 
-## General Troubleshooting Notes
+## General troubleshooting notes
 
 The troubleshooting process and Work object inspection are identical for both placement types:
+
 - Both use the same underlying Work API to apply resources to member clusters.
 - The Work object status and manifestConditions have the same structure regardless of the placement type that created them.
 - The `Available` condition in the Work status indicates whether the applied resources are now available on the member cluster.
 - The main difference is the scope: the cluster-scoped placement can select both cluster-scoped and namespace-scoped resources, while the namespace-scoped placement can only select namespace-scoped resources within its own namespace.
 
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
-

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

@@ -9,6 +9,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 
 # Resource propagation failure: PlacementOverridden is False
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementOverridden` for ClusterResourcePlacement
@@ -205,7 +207,7 @@ jsonPatchOverrides:
 
 The code adds the new label `newlabel` that has the value `new-value` to the ClusterRole `secret-reader`.
 
-## General Notes
+## General notes
 
 For ResourcePlacement, the override flow is identical except that all the resources reside in the same namespace. Use `ResourceOverride` instead of `ClusterResourceOverride` and expect `ResourcePlacementOverridden` in conditions.
 

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

@@ -8,6 +8,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 ---
 # Resource propagation failure: PlacementRolloutStarted is false
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementRolloutStarted` for ClusterResourcePlacement
@@ -404,9 +406,7 @@ After you create the `test-ns` namespace on the hub cluster, the rollout control
 
 In this situation, to address this issue, consider manually setting `maxUnavailable` to a value greater than `1` to relax the `RollingUpdate` configuration. Alternatively, you can join a third member cluster.
 
-## General Notes
+## General notes
 
 The rollout failure investigation flow is identical for ClusterResourcePlacement and ResourcePlacement. Only the snapshot object kind differs. Replace ClusterResourcePlacement (CRP)-specific object kinds with their ResourcePlacement (RP) equivalents when working with namespace-scoped placements.
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
-

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

@@ -8,6 +8,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 ---
 # Resource propagation failure: PlacementScheduled is false
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementScheduled` for ClusterResourcePlacement
@@ -244,8 +246,7 @@ status:
 
 In this scenario, to resolve this issue, add the `env:prod` label to the member cluster resource for `kind-cluster-2` as well, so that the scheduler can select the cluster to propagate resources.
 
-## General Notes
-The scheduling failure investigation flow is identical for ClusterResourcePlacement and ResourcePlacement; only the snapshot object kind differs. Replace ClusterResourcePlacement (CRP)-specific object kinds with their ResourcePlacement (RP) equivalents when working with namespace-scoped placements.
+## General notes
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+The scheduling failure investigation flow is identical for ClusterResourcePlacement and ResourcePlacement; only the snapshot object kind differs. Replace ClusterResourcePlacement (CRP)-specific object kinds with their ResourcePlacement (RP) equivalents when working with namespace-scoped placements.
 

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

@@ -8,6 +8,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 ---
 # Resource propagation failure: WorkSynchronized is false
 
+## Summary
+
 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:
 
 - `ClusterResourcePlacementWorkSynchronized` for ClusterResourcePlacement
@@ -165,8 +167,7 @@ In this situation, here are several potential solutions:
 
 In other situations, you might opt to wait for the work to finish propagating.
 
-## General Notes
-For ResourcePlacement, the investigation is identical—inspect `.status.placementStatuses[*].conditions` for `WorkSynchronized` and check the associated Work in the `fleet-member-{clusterName}` namespace.
+## General notes
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+For ResourcePlacement, the investigation is identical—inspect `.status.placementStatuses[*].conditions` for `WorkSynchronized` and check the associated Work in the `fleet-member-{clusterName}` namespace.
 

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

@@ -9,6 +9,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 
 # Troubleshooting ClusterResourcePlacement API in Azure Kubernetes Fleet Manager
 
+## Summary
+
 This troubleshooting guide helps you resolve `ClusterResourcePlacement` API object-related issues when you use Azure Kubernetes Fleet Manager. Troubleshooting these errors on the hub cluster requires knowledge of the following objects:
 
 - `ClusterResourceSnapshot`
@@ -160,6 +162,4 @@ To find the correct work resource, follow these steps:
     ```
 
    > [!NOTE]  
-   > In this command, replace `{clusterName}` and `{CRPName}` with the names that you identified in the first step.
-
- 
+   > In this command, replace `{clusterName}` and `{CRPName}` with the names that you identified in the first step.

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

@@ -10,6 +10,8 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 
 # Troubleshooting ResourcePlacement API in Azure Kubernetes Fleet Manager (preview)
 
+## Summary
+
 This troubleshooting guide helps you resolve `ResourcePlacement` API object-related issues when you use Azure Kubernetes Fleet Manager. Troubleshooting these errors on the hub cluster requires knowledge of the following objects:
 
 - `ResourceSnapshot`
@@ -230,5 +232,3 @@ To find the correct work resource, follow these steps:
 
    > [!NOTE]
    > In this command, replace `{clusterName}` and `{RPName}` with the names that you identified in the first step.
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]