Skip to content

Commit 5e8c33b

Browse files
Deland-HanDeland-Han
authored
Merge pull request #9005 from MicrosoftDocs/main
Auto push to live 2025-05-27 02:32:18
2 parents fa1d8b8 + ae437f1 commit 5e8c33b

14 files changed

+402
-27
lines changed

‎support/azure/.openpublishing.redirection.azure.json‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6322,8 +6322,38 @@
63226322
"redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/zonalallocation-allocationfailed-error"
63236323
},
63246324
{
6325+
6326+
"source_path": "kubernetes-fleet/troubleshoot-clusterresourceplacement-api-issues.md",
6327+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/troubleshoot-clusterresourceplacement-api-issues"
6328+
},
6329+
{
6330+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementscheduled-false.md",
6331+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementscheduled-false"
6332+
},
6333+
{
6334+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementrolloutstarted-false.md",
6335+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementrolloutstarted-false"
6336+
},
6337+
{
6338+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementoverridden-false.md",
6339+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementoverridden-false"
6340+
},
6341+
{
6342+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementworksynchronized-false.md",
6343+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementworksynchronized-false"
6344+
},
6345+
{
6346+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementapplied-false.md",
6347+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementapplied-false"
6348+
},
6349+
{
6350+
"source_path": "kubernetes-fleet/crp-clusterresourceplacementavailable-false.md",
6351+
"redirect_url": "/troubleshoot/azure/kubernetes-fleet/cluster-resource-placement/crp-clusterresourceplacementavailable-false"
6352+
},
6353+
{
63256354
"source_path": "hpc/batch/error-accountencryptionkeyunavailable.md",
63266355
"redirect_url": "/troubleshoot/azure/hpc/batch/welcome-hpc-batch"
6356+
63276357
}
63286358
]
63296359
}

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -262,4 +262,4 @@ In this situation, a potential solution is to set the `AllowCoOwnership` to `tru
262262

263263
Additionally, you can review the logs for the [Apply Work Controller](https://github.com/Azure/fleet/blob/main/pkg/controllers/work/apply_controller.go) for more insights into why the resources are unavailable.
264264

265-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
265+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,4 +221,5 @@ In this situation, a potential solution is to check the deployment in the member
221221
222222
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.
223223
224-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
224+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
225+

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,4 +173,5 @@ jsonPatchOverrides:
173173

174174
This adds the new label `newlabel` that has the value `new-value` to the ClusterRole `secret-reader`.
175175

176-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
176+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
177+

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -369,4 +369,5 @@ Upon creating the `test-ns` namespace on the hub cluster, the rollout controller
369369

370370
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.
371371

372-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
372+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
373+

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,4 +214,5 @@ status:
214214
215215
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.
216216

217-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
217+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
218+

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,4 +136,5 @@ In this situation, here are several potential solutions:
136136

137137
In other situations, you might opt to wait for the work to finish propagating.
138138

139-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
139+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
140+

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ 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
---
9+
910
# Troubleshooting ClusterResourcePlacement API in Azure Kubernetes Fleet Manager
1011

1112
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:
@@ -15,7 +16,7 @@ This troubleshooting guide helps you resolve `ClusterResourcePlacement` API obje
1516
- `ClusterResourceBinding`
1617
- `Work`
1718

18-
For more details about each object, see the [API reference](https://github.com/Azure/fleet/blob/main/docs/api-references.md).
19+
For more details about each object, see the [KubeFleet API reference](https://kubefleet-dev.github.io/website/docs/api-reference/).
1920

2021
## Complete progression of the ClusterResourcePlacement deployment
2122

@@ -161,4 +162,4 @@ To find the correct work resource, follow these steps:
161162
> [!NOTE]
162163
> In this command, replace `{clusterName}` and `{CRPName}` with the names that you identified in the first step.
163164

164-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
165+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

0 commit comments

Comments
 (0)