You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Frequently Asked Questions - Azure Arc-enabled Kubernetes and GitOps
14
12
15
-
This article addresses frequently asked questions about Azure Arc-enabled Kubernetes.
13
+
This article addresses frequently asked questions about Azure Arc-enabled Kubernetes and GitOps.
16
14
17
15
## What is the difference between Azure Arc-enabled Kubernetes and Azure Kubernetes Service (AKS)?
18
16
@@ -81,32 +79,6 @@ This feature applies baseline configurations (like network policies, role bindin
81
79
82
80
The compliance state of each GitOps configuration is reported back to Azure. This lets you keep track of any failed deployments.
83
81
84
-
## Error installing the microsoft.flux extension (Flux v2)
85
-
86
-
The `microsoft.flux` extension installs the Flux controllers and Azure GitOps agents into your Azure Arc-enabled Kubernetes or AKS clusters. If you experience an error during installation below are some troubleshooting actions.
87
-
88
-
* Error message
89
-
90
-
```console
91
-
{'code':'DeploymentFailed','message':'At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.','details':[{'code':'ExtensionCreationFailed','message':' Request failed to https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.ContainerService/managedclusters/<CLUSTER_NAME>/extensionaddons/flux?api-version=2021-03-01. Error code: BadRequest. Reason: Bad Request'}]}
92
-
```
93
-
94
-
* For AKS cluster, assure that the subscription has the following feature flag enabled: `Microsoft.ContainerService/AKS-ExtensionManager`.
95
-
96
-
```console
97
-
az feature register --namespace Microsoft.ContainerService --name AKS-ExtensionManager
98
-
```
99
-
100
-
* Force delete the extension.
101
-
102
-
```console
103
-
az k8s-extension delete --force -g <RESOURCE_GROUP> -c <CLUSTER_NAME> -n flux -t <managedClusters OR connectedClusters>
104
-
```
105
-
106
-
* Assure that the cluster does not have any policies that restrict creation of the `flux-system` namespace or resources in that namespace.
107
-
108
-
After you have verified the above, you can re-install the extension.
109
-
110
82
## Does Azure Arc-enabled Kubernetes store any customer data outside of the cluster's region?
111
83
112
84
The feature to enable storing customer data in a single region is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo and Brazil South (Sao Paulo State) Region of Brazil Geo. For all other regions, customer data is stored in Geo. For more information, see [Trust Center](https://azure.microsoft.com/global-infrastructure/data-residency/).
# Azure Arc-enabled Kubernetes and GitOps troubleshooting
13
13
14
-
This document provides troubleshooting guides for issues with connectivity, permissions, and agents.
14
+
This document provides troubleshooting guides for issues with Azure Arc-enabled Kubernetes connectivity, permissions, and agents. It also provides troubleshooting guides for Azure GitOps, which can be used in either Azure Arc-enabled Kubernetes or Azure Kubernetes Service (AKS) clusters.
15
15
16
16
## General troubleshooting
17
17
@@ -216,12 +216,15 @@ metadata:
216
216
217
217
### Installing the `microsoft.flux` extension (Flux v2)
218
218
219
-
If the `microsoft.flux` extension is in a failed state, you can run a script to investigate. The cluster-type parameter can be set to `connectedClusters` for Arc cluster or `managedClusters` for AKS cluster. The name of the `microsoft.flux` extension will be "flux" if the extension was installed automatically during creation of a `fluxConfigurations` resource. Look in the "statuses" object for information.
219
+
The `microsoft.flux` extension installs the Flux controllers and Azure GitOps agents into your Azure Arc-enabled Kubernetes or Azure Kubernetes Service (AKS) clusters. If the extension is not already installed in a cluster and you create a GitOps configuration resource for that cluster, the extension will be installed automatically.
220
+
221
+
If you experience an error during installation or if the extension is in a failed state, you can first run a script to investigate. The cluster-type parameter can be set to `connectedClusters` for an Arc-enabled cluster or `managedClusters` for an AKS cluster. The name of the `microsoft.flux` extension will be "flux" if the extension was installed automatically during creation of a GitOps configuration. Look in the "statuses" object for information.
220
222
221
223
One example:
222
224
223
225
```console
224
-
az k8s-extension show --resource-group RESOURCE_GROUP --cluster-name CLUSTER_NAME --cluster-type connectedClusters -n flux
226
+
az k8s-extension show -g <RESOURCE_GROUP> -c <CLUSTER_NAME> -n flux -t <connectedClusters or managedClusters>
227
+
flux
225
228
226
229
...
227
230
"statuses": [
@@ -238,7 +241,7 @@ az k8s-extension show --resource-group RESOURCE_GROUP --cluster-name CLUSTER_NAM
238
241
Another example:
239
242
240
243
```console
241
-
az k8s-extension show --resource-group RESOURCE_GROUP --cluster-name CLUSTER_NAME --cluster-type connectedClusters -n flux
244
+
az k8s-extension show -g <RESOURCE_GROUP> -c <CLUSTER_NAME> -n flux -t <connectedClusters or managedClusters>
242
245
243
246
"statuses": [
244
247
{
@@ -251,19 +254,37 @@ az k8s-extension show --resource-group RESOURCE_GROUP --cluster-name CLUSTER_NAM
251
254
]
252
255
```
253
256
254
-
In both of these cases, delete the `flux-system` namespace and uninstall the Helm release. This should resolve the extension installation issue.
257
+
Another example from the portal:
255
258
256
259
```console
257
-
kubectl delete namespaces flux-system -A
258
-
helm uninstall flux -n -flux-system
260
+
{'code':'DeploymentFailed','message':'At least one resource deployment operation failed. Please list
261
+
deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.
262
+
','details':[{'code':'ExtensionCreationFailed', 'message':' Request failed to https://management.azure.com/
If that doesn't resolve the issue, you can delete the extension. After deleting the extension, you can either [re-create a flux configuration](./tutorial-use-gitops-flux2.md) which will install the flux extension automatically or you can re-install the flux extension manually.
268
+
For all these cases, possible remediation actions are to force delete the extension, uninstall the Helm release, and delete the `flux-system` namespace from the cluster.
az k8s-extension delete --force -g <RESOURCE_GROUP> -c <CLUSTER_NAME> -n flux -t <managedClusters OR connectedClusters>
272
+
helm uninstall flux -n flux-system
273
+
kubectl delete namespaces flux-system
265
274
```
266
275
276
+
Some other aspects to consider:
277
+
278
+
* For AKS cluster, assure that the subscription has the following feature flag enabled: `Microsoft.ContainerService/AKS-ExtensionManager`.
279
+
280
+
```console
281
+
az feature register --namespace Microsoft.ContainerService --name AKS-ExtensionManager
282
+
```
283
+
284
+
* Assure that the cluster does not have any policies that restrict creation of the `flux-system` namespace or resources in that namespace.
285
+
286
+
With these actions accomplished you can either [re-create a flux configuration](./tutorial-use-gitops-flux2.md) which will install the flux extension automatically or you can re-install the flux extension manually.
287
+
267
288
## Monitoring
268
289
269
290
Azure Monitor for containers requires its DaemonSet to be run in privileged mode. To successfully set up a Canonical Charmed Kubernetes cluster for monitoring, run the following command:
0 commit comments