Skip to content

Commit

Permalink
Merge pull request #433 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
1/8/2025 11:00 AM IST Publish
  • Loading branch information
PhilKang0704 authored Jan 8, 2025
2 parents 9f12cef + 0618865 commit 0c86b6c
Show file tree
Hide file tree
Showing 4 changed files with 12 additions and 22 deletions.
2 changes: 1 addition & 1 deletion articles/azure-arc/kubernetes/agent-upgrade.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Upgrade Azure Arc-enabled Kubernetes agents"
ms.date: 12/13/2023
ms.date: 01/07/2025
ms.topic: how-to
ms.custom: devx-track-azurecli
description: "Control agent upgrades for Azure Arc-enabled Kubernetes"
Expand Down
28 changes: 9 additions & 19 deletions articles/azure-arc/kubernetes/extensions-troubleshooting.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters"
ms.date: 12/19/2023
ms.date: 01/07/2025
ms.topic: how-to
ms.custom: devx-track-azurecli
description: "Learn how to resolve common problems with Azure Arc-enabled Kubernetes cluster extensions."
Expand Down Expand Up @@ -42,11 +42,7 @@ For an AKS cluster, ensure that the `Microsoft.ContainerService/AKS-ExtensionMan
az feature register --namespace Microsoft.ContainerService --name AKS-ExtensionManager
```

Next, run the following command to determine if there are other problems.

In the command, for an Azure Arc-enabled cluster, set the cluster type parameter (`-t`) to `connectedClusters`. For an AKS cluster, set `-t` to `managedClusters`.

The name of the `microsoft.flux` extension is `flux` if the extension was installed automatically when you created your GitOps configuration.
Next, run the following command to determine if there are other problems. Set the cluster type parameter (`-t`) to `connectedClusters` for For an Azure Arc-enabled cluster, or to `managedClusters` for an AKS cluster. If the extension was installed automatically when you created your GitOps configuration, the name of the `microsoft.flux` extension is `flux`.

```azurecli
az k8s-extension show -g <RESOURCE_GROUP> -c <CLUSTER_NAME> -n flux -t <connectedClusters or managedClusters>
Expand Down Expand Up @@ -76,21 +72,11 @@ The extension status returns as `Failed`:

In this case, the `extension-agent` pod tries to get its token from Azure Instance Metadata Service on the cluster, but the token request is intercepted by the [pod identity](/azure/aks/use-azure-ad-pod-identity). To fix this problem, [upgrade to the latest version](extensions.md#upgrade-an-extension-instance) of the `microsoft.flux` extension.

### Issues with kubelet identity when you install the microsoft.flux extension in an AKS cluster

One of the authentication options in an AKS cluster is to use a *kubelet identity* as a user-assigned managed identity. By choosing to use a kubelet identity, you can help reduce operational overhead and increase security when users connect to Azure resources like Azure Container Registry.

To set Flux to use a kubelet identity, add the parameter `--config useKubeletIdentity=true` when you install the Flux extension:

```console
az k8s-extension create --resource-group <resource-group> --cluster-name <cluster-name> --cluster-type managedClusters --name flux --extension-type microsoft.flux --config useKubeletIdentity=true
```

### Have minimum required memory and CPU resources to install the microsoft.flux extension
### Memory and CPU resource requirements for installing the microsoft.flux extension

The controllers that are installed in your Kubernetes cluster when you install the `microsoft.flux` extension require minimum CPU and memory resources to properly schedule on a Kubernetes cluster node. Be sure that your cluster meets the minimum memory and CPU resources requirements.
The controllers that are installed in your Kubernetes cluster when you install the `microsoft.flux` extension must have enough CPU and memory resources to properly schedule on a Kubernetes cluster node. Be sure that your cluster meets the minimum memory and CPU resource requirements.

The following table lists the minimum and maximum limits for potential CPU and memory resource requirements in this scenario:
The following table lists the minimum and maximum limits for potential CPU and memory resource requirements for this scenario:

| Container name | Minimum CPU | Minimum memory | Maximum CPU | Maximum memory |
| -------------- | ----------- | -------- |
Expand Down Expand Up @@ -285,6 +271,8 @@ For OSM to function, there must be at least one endpoint for `osm-injector`. The

### Check webhooks: Validating and Mutating

Check the **Validating** webhook by running the following command:

```bash
kubectl get ValidatingWebhookConfiguration --selector app=osm-controller
```
Expand All @@ -296,6 +284,8 @@ NAME WEBHOOKS AGE
osm-validator-mesh-osm 1 81m
```

Check the **Mutating** webhook by running the following command:

```bash
kubectl get MutatingWebhookConfiguration --selector app=osm-injector
```
Expand Down
2 changes: 1 addition & 1 deletion articles/azure-arc/kubernetes/tutorial-use-gitops-flux2.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,7 +572,7 @@ az k8s-extension update --resource-group <resource-group> --cluster-name <cluste

Support for vertical scaling is available starting with [`microsoft.flux` v1.12.0](extensions-release.md#flux-gitops). Currently, only specific parameters described in the [Flux vertical scaling documentation](https://fluxcd.io/flux/installation/configuration/vertical-scaling/) are natively supported. Other parameters may be manually applied to the cluster.

To increase resource limits on controllers beyond the [current limits](extensions-troubleshooting.md#have-minimum-required-memory-and-cpu-resources-to-install-the-microsoftflux-extension), run this command, changing the specific resource type and value as needed:
To increase resource limits on controllers beyond the [current limits](extensions-troubleshooting.md#memory-and-cpu-resource-requirements-for-installing-the-microsoftflux-extension), run this command, changing the specific resource type and value as needed:

```azurecli
az k8s-extension update --resource-group <resource-group> --cluster-name <cluster-name> --cluster-type <cluster-type> --name flux --config kustomize-controller.resources.limits.memory=2Gi kustomize-controller.resources.limits.cpu=2000m
Expand Down
2 changes: 1 addition & 1 deletion articles/azure-arc/kubernetes/validation-program.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Azure Arc-enabled Kubernetes validation"
ms.date: 10/26/2023
ms.date: 01/07/2025
ms.topic: how-to
description: "Describes Arc validation program for Kubernetes distributions"
---
Expand Down

0 comments on commit 0c86b6c

Please sign in to comment.