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:
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 |
| Cross-cluster networking | ✅ Preview | ❌ Unsupported |
| Workload placement | ✅ GA | ✅ GA |
| DNS load balancing | ✅ GA | ❌ Unsupported |
| Managed Namespaces | ✅ GA | ❌ Unsupported |
| Managed Namespace RBAC | ✅ GA | ❌ Unsupported |
Arc-enabled Kubernetes clusters important considerations
Depending on your environment and configuration, certain limitations might 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 member cluster must meet the following conditions:
- At least 210 MB memory and 2% of one CPU core available.
- Reserve 3 pods for the Azure Kubernetes Fleet Manager Arc extension agents.
- Create the fleet-system namespace for Fleet-related components and don't directly modify it.
Networking
TLS-terminating proxies aren't supported.