Skip to content

Commit 7563746

Browse files
Merge pull request #234918 from JnHs/jh-arck8-tsminmem
add minimum cpu and memory
2 parents e9fae5c + 979a97b commit 7563746

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/azure-arc/kubernetes/troubleshooting.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Troubleshoot common Azure Arc-enabled Kubernetes issues"
3-
ms.date: 03/28/2023
3+
ms.date: 04/18/2023
44
ms.topic: how-to
55
ms.custom: devx-track-azurecli
66
description: "Learn how to resolve common issues with Azure Arc-enabled Kubernetes clusters and GitOps."
@@ -375,19 +375,19 @@ az k8s-extension create --resource-group <resource-group> --cluster-name <cluste
375375

376376
### Flux v2 - `microsoft.flux` extension installation CPU and memory limits
377377

378-
The controllers installed in your Kubernetes cluster with the Microsoft Flux extension require the following CPU and memory resource limits to properly schedule on Kubernetes cluster nodes.
378+
The controllers installed in your Kubernetes cluster with the Microsoft Flux extension require CPU and memory resources to properly schedule on Kubernetes cluster nodes. This table shows the minimum memory and CPU resources that may be requested, along with the maximum limits for potential CPU and memory resource requirements.
379379

380-
| Container Name | CPU limit | Memory limit |
380+
| Container Name | Minimum CPU | Minimum memory | Maximum CPU | Maximum memory |
381381
| -------------- | ----------- | -------- |
382-
| fluxconfig-agent | 50 m | 150 Mi |
383-
| fluxconfig-controller | 100 m | 150 Mi |
384-
| fluent-bit | 20 m | 150 Mi |
385-
| helm-controller | 1000 m | 1 Gi |
386-
| source-controller | 1000 m | 1 Gi |
387-
| kustomize-controller | 1000 m | 1 i |
388-
| notification-controller | 1000 m | 1 Gi |
389-
| image-automation-controller | 1000 m | 1 Gi |
390-
| image-reflector-controller | 1000 m | 1 Gi |
382+
| fluxconfig-agent | 5 m | 30 Mi | 50 m | 150 Mi |
383+
| fluxconfig-controller | 5 m | 30 Mi | 100 m | 150 Mi |
384+
| fluent-bit | 5 m | 30 Mi | 20 m | 150 Mi |
385+
| helm-controller | 100 m | 64 Mi | 1000 m | 1 Gi |
386+
| source-controller | 50 m | 64 Mi | 1000 m | 1 Gi |
387+
| kustomize-controller | 100 m | 64 Mi | 1000 m | 1 Gi |
388+
| notification-controller | 100 m | 64 Mi | 1000 m | 1 Gi |
389+
| image-automation-controller | 100 m | 64 Mi | 1000 m | 1 Gi |
390+
| image-reflector-controller | 100 m | 64 Mi | 1000 m | 1 Gi |
391391

392392
If you've enabled a custom or built-in Azure Gatekeeper Policy that limits the resources for containers on Kubernetes clusters, such as `Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits`, ensure that either the resource limits on the policy are greater than the limits shown above or that the `flux-system` namespace is part of the `excludedNamespaces` parameter in the policy assignment.
393393

0 commit comments

Comments
 (0)