Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Kubernetes Fleet Manager supports two types of member clusters:
Important
Azure Kubernetes Fleet Manager's support for Arc-enabled Kubernetes clusters is currently in Preview.
The following table outlines which Azure Kubernetes Fleet Manager capabilities are supported for each member cluster type.
| Capability | AKS cluster | Arc-enabled Kubernetes cluster |
|---|---|---|
| Kubernetes and node image updates | ✅ GA | ❌ Unsupported |
| Workload placement | ✅ GA | ✅ Preview |
| DNS load balancing | ✅ GA | ❌ Unsupported |
| Managed Namespaces | ✅ Preview | ✅ Preview |
| Managed Namespace RBAC | ✅ Preview | ❌ Unsupported |
Arc-enabled Kubernetes Clusters important considerations
Depending on your environment and configuration, certain limitations may apply when connecting an Arc-enabled Kubernetes cluster to an Azure Kubernetes Fleet Manager hub. Review the following considerations:
Cluster resource requirements
When you add an Arc-enabled Kubernetes cluster to Fleet Manager, the following conditions apply on the member cluster:
- At least 210 MB memory and 2% of one CPU core available.
- The cluster should reserve 3 pods for the Azure Kubernetes Fleet Manager Arc extension agents.
- The fleet-system namespace is created for Fleet-related components and shouldn't be directly modified.
Networking
TLS-terminating proxies are not supported.